Huawei HLR9820 Function

Function description of HLR9820 V900R003C04
Huawei HLR9820 Function Description

(GSM&UMTS)

HLR9820
V900R003C04

Issue 1.00
Date 2008Q2
INTERNAL


Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, 518129, Peoples Republic of China
Website: http://www.huawei.com
Email: support@huawei.com


Contents
1 Huawei HLR9820V900R003C03 Function Description (GSM & UMTS)........................... 4
1.1 Basic Function Description................................................................................................................................. 4
1.2 Optional function description.............................................................................................................................. 6
1.2.2 Supplementary Services............................................................................................................................. 8
1.2.3 ODB Service ............................................................................................................................................ 24
1.2.4 Other Services .......................................................................................................................................... 36
1.2.5 Mobility Services ..................................................................................................................................... 39
1.2.6 Call Handling Services ............................................................................................................................ 50
1.2.7 Supplementary Service Related Services ................................................................................................ 53
1.2.8 Subscriber Data Management.................................................................................................................. 58
1.2.9 Protocol Interfaces Function.................................................................................................................... 68
1.2.10 Operation and Maintenance Functions.................................................................................................. 72
1.2.11 Reliability Functions.............................................................................................................................. 82
1.2.12 Authentication Functions ....................................................................................................................... 89
1.2.13 CS Data Services.................................................................................................................................... 94
1.2.14 GPRS Services ....................................................................................................................................... 95
1.2.15 Supplementary Services......................................................................................................................... 97
1.2.16 CAMEL Services ................................................................................................................................. 101
1.2.17 Location Services (LCS)...................................................................................................................... 104
1.2.18 Other Services ...................................................................................................................................... 105
1.2.19 Mobility Services ................................................................................................................................. 108
1.2.20 Subscriber Data Management.............................................................................................................. 110
1.2.21 Networking Functions.......................................................................................................................... 113
1.2.22 Enhanced Functions............................................................................................................................. 117
1.2.23 GSMR Functions.................................................................................................................................. 136
1.2.24 Redundancy Functions......................................................................................................................... 144
1.3 Additional Function Description..................................................................................................................... 149
1.4 Virtual HLR Function...................................................................................................................................... 164


1 Huawei HLR9820V900R003C03
Function Description (GSM & UMTS)
This document briefly describes the functions of the HLR9820 product, and is
intended to help the user understand the functions of the product.
1.1 Basic Function Description
WHFD-020000
Function name:
Teleservices
Function description:
The HLR provides standard Teleservices, including Speech Service (WHFD-
020100)

WHFD-020100
Function name:
Speech Service
The speech service is the basic service of the telecommunication network,
including Telephony (TS11) (WHFD-020101) and Emergency Call (TS12) (WHFD-
020102).


WHFD-020101
Function name:
Telephony (TS11)
Specifications:
3GPP29002, 3GPP22003
Overview:
Through the service, the carrier can establish call connections between the PSTN
network subscribers, ISDN network subscribers, and PLMN network subscribers.
The HLR supports subscribing to the service and modifying data of the 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.
Benefits:

Benefits for the carrier:
The function allows the carrier to add subscribers to different basic service groups,
and increase network traffics volume, thus increasing the revenue.

Benefits for the subscriber:
The function allows the subscriber to enjoy basic voice service.
Requirements for other NEs:
The HLR realizes the function in compliance with the standard protocol. There is
no special requirement for other NEs.

WHFD-020102
Function name:
Emergency Call (TS12)
Specifications:
3GPP29002, 3GPP22003
Overview:
The function allows a subscriber to make an emergency call. For example, dial
112 and 119. When a subscriber is not registered or calls into/from the subscriber
are barred, the subscriber can make an emergency call.
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.
Benefits:



The function allows the carrier to provide emergency call service for the
subscribers.

The function allows the subscriber to make an emergency call for helps.

1.2 Optional function description
WHFD-020200
Function name:
Short Message Service (SMS)
In every short message, the length of the cell is very short. According to the
technical specifications of the ETSI GSM (such as ETSI GSM 03.40 and ETSI
GSM 03.41), a point to point (P2P) short message can be as long as 140 bytes,
which is equivalent to 160 ASCII characters or 70 Chinese characters; a broadcast
short message can be 15 pages long, with every paging containing 82 bytes
(which is equivalent to 92 ASCII characters or 41 Chinese characters).The P2P
SMS service allows subscribers to send or receive short messages at any time. The
broadcast SMS service allows subscribers to receive public information regularly
and selectively.
The short message service includes:

P2P SMS service, which includes Short Message MT/PP (TS21) (WHFD-
020201) and Short Message MO/PP (TS22) (WHFD-020202)

The P2MP SMS service. It mainly refers to the cell broadcast SMS service.

WHFD-020201
Function name:
Short Message MT/PP (TS21)
Specifications:
3GPP29002, 3GPP23039, 3GPP23040, 3GPP23041, 3GPP24011, 3GPP24012
Overview:


The Short Message MT/PP service refers to the service that enables the short
message center (SMC) to send short messages to the MS.
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, the SMC sends a message to the HLR, requesting it to feed back
the MSC number or SGSN number of the callee. Upon receiving the request, the
HLR returns a message based on the subscription information and current status
of the subscriber.
To improve the success rate in receiving short message, the HLR allows you to
configure the short message transmission route for subscribers adopting the
network 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
and MSC 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.
Benefits:

The service can boost the traffics volume and increase the average revenue per user
(ARPU).

The service diversifies the communication modes. When voice conversation is
inconvenient, the subscriber can keep contact with others through short messages.
The HLR realizes the function in compliance with the standard protocols. The
SMC equipment is deployed in the network.

WHFD-020202
Function name:
Short Message MO/PP (TS22)
Specifications:
3GPP29002, 3GPP23039, 3GPP23040, 3GPP23041, 3GPP24011, 3GPP24012
Overview:
The Short Message MO/PP service refers to the service that enables the MS to
send short message to the SMC.
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.
Benefits:

The service can increase the traffics volume and increase the ARPU.

The service diversifies the communication modes. When voice conversation is
inconvenient, the subscriber can keep contact with others through short messages.
The HLR realizes the function in compliance with the standard protocol. The
SMC equipment is deployed in the network.

1.2.2 Supplementary Services
WHFD-030000
Function name:
Supplementary Services
The HLR 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)

WHFD-030100
Function name:
Call Forwarding (CF) Services
The CF services include:


Call Forwarding Unconditional (CFU) (WHFD-030101)

Call Forwarding on Mobile Subscriber Busy (CFB) (WHFD-030102)

Call Forwarding on no Reply (CFNRy) (WHFD-030103)

Call Forwarding on Mobile Subscriber not Reachable (CFNRc) (WHFD-
030104)

WHFD-030101
Function name:
Call Forwarding Unconditional (CFU)
Specifications:
3GPP29002, 3GPP22082, 3GPP23082, 3GPP24082
Overview:
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).
The HLR supports subscribing/withdrawing and activating/deactivating the
service. Meanwhile, the HLR stores the Ftn numbers registered by the subscriber,
and carries the Ftn numbers in the response message to the routing message from
the GMSC. By contacting the business hall, the subscriber can activate the service.
Benefits:

The carrier can forward calls more flexibly and increase call completion rate, thus
boosting the revenue.

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. The service provides more means for the subscriber to enjoy the
telecommunication service.
WHFD-030102
Function name:
Call Forwarding on Mobile Subscriber Busy (CFB)
Specifications:


3GPP29002, 3GPP22082, 3GPP23082, 3GPP24082
Overview:
According to causes of call forwarding, the CFB service can be further divided
into call forwarding on busy due to network cause and call forwarding on busy
due to subscriber's cause. 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).
service. The HLR stores the Ftn numbers. When the location of a subscriber
changes, the HLR sends the Ftn numbers 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 number, 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 the carrier.
Benefits:


WHFD-030103
Function name:
Call Forwarding on no Reply (CFNRy)
Specifications:
3GPP29002, 3GPP22082, 3GPP23082, 3GPP24082
Overview:
When an incoming call to a mobile subscriber keeps unanswered for a long time
or the no-replay timer times out, the call is forwarded to a third party subscriber.
The third party can be either a PLMN/PSTN/ISDN subscriber or a service console
(such as voice mailbox).


service. The HLR stores the Ftn numbers. When the location of a subscriber
changes, the HLR sends the Ftn numbers 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 number, 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 the carrier.
Benefits:


WHFD-030104
Function name:
Call Forwarding on Mobile Subscriber not Reachable (CFNRc)
Specifications:
3GPP29002, 3GPP22082, 3GPP23082, 3GPP24082
Overview:
When the wireless connection between the network and a mobile subscriber is
interrupted, if there is an incoming call, the call is forwarded to a third party
subscriber. The third party can be either a PLMN/PSTN/ISDN subscriber or a
service console (such as voice mailbox).
The HLR supports subscribing/withdrawing and activating/deactivating the service.
To use the service, the subscriber must register the service in the business hall of
the carrier, 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:
1. 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.
2.
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 number 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 number in the returned message. If the HLR
does not know the reason why the subscriber is unreachable, it does not send the
Ftn number 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.
Benefits:


If the MS of a subscriber is turned off or the quality of the signals received by the
MS is very poor, the subscriber can forward an incoming call to another MS
without affecting the conversation.

WHFD-030105
Function name:
Forwarded-to Number Analysis and Regulation
Specifications:
None.
Overview:
This function allows you to configure the forwarding service data in the HLR.
When a subscriber registers the forwarding service, Ftn numbers of correct format
can be generated and stored in the databases of the HLR.
The request for registering the call forwarding service received by the HLR
contains Ftn numbers. These Ftn numbers adopt the following formats:

Unknown format (or domestic format): 81 + Ftn number inputted by the
subscriber:


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 number registered in the MS adopts the unknown format. The
HLR regulates the received Ftn numbers. The Ftn numbers saved in the database
and those sent to the MS adopt the international format. You can only judge the
attribute of a regulated Ftn number, for example, check whether the Ftn is in the
homeland or the Ftn is in the local network. To regulate the Ftn numbers, you
need to configure the related data in the HLR.
Enhanced function description:
To enable the HLR to regulate the Ftn numbers, you need to configure the
following table data.
1. INTRA_OFFICE table
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 number 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 number.
2. IMSICODE_DATA table
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
Ftn number 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 number.
3. CALLEDNUM_ANALYSIS table
The table contains multiple records. Every record has four fields: prefix of the Ftn
number, attribute of the Ftn number, number of information station or not, and
number of entertainment station or not. There are four options for the Ftn number
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 number with records of the CALLEDNUM_ANALYSIS table to
find a matched record, and then regulates the Ftn number according to the record.
4. DOMESTICAREA_DATA table
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.
5. ISDNCODE_DATA table
The table contains multiple records, with each record describing an MSISDN
prefix and its corresponding area code. When analyzing a PLMN Ftn number, the


HLR queries the table to check whether the Ftn number exceeds area limitation
imposed on the call forwarding.
6. INTAREA_DATA table
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 number of international format, the HLR queries the table to
verify whether the Ftn number is a domestic number.
7. FORBIDFWD_NUM table
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 number.
Benefits:

The function allows the carrier to configure the call forwarding service flexibly.

None.
The HLR realizes the function internally. There is no special requirement for other
NEs.

WHFD-030200
Function name:
Call Barring Services
The call barring services can be divided into two categories: incoming call barring
service and outgoing call barring service. The HLR provides the following
standard call barring services:

Barring of All Outgoing Calls (BAOC) (WHFD-030201)

Barring of Outgoing International Calls (BOIC) (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 Incoming Calls when Roaming Outside the Home PLMN Country
(BIC-ROAM) (WHFD-030205)


WHFD-030201
Function name:
Barring of All Outgoing Calls (BAOC)
Specifications:
3GPP29002, 3GPP22088, 3GPP23088, 3GPP24088
Overview:
When the service is activated, the subscriber cannot make any call except
emergency calls.
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.
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 the carrier. 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.
Benefits:

The service expands the business scope of the carrier and increases service
benefits.

The service allows the subscriber to bar outgoing international calls flexibly.

WHFD-030202
Function name:
Barring of Outgoing International Calls (BOIC)
Specifications:
3GPP29002, 3GPP22088, 3GPP23088, 3GPP24088
Overview:


When the service is activated, if the subscriber roams in the home PLMN country,
the subscriber is prohibited to make an international call.
To bar all outgoing international calls from a subscriber, the HLR stores the code
and status information of the BOIC service, and sends them to the VLR of the
subscriber. The MSC implements the barring of outgoing international calls for
the subscriber. The HLR supports subscribing/withdrawing and
activating/deactivating the service. The subscriber can modify and query the
status of the service in the MS. Meanwhile, the HLR can specify whether the right
of configuring the BOIC service is under the control of the subscriber or the
carrier. If the right is under the control of the subscriber, the subscriber can
activate/deactivate the service through the 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.
Benefits:

benefits.

The service allows the subscriber to bar various calls flexibly.

WHFD-030203
Function name:
Barring of Outgoing International Calls Except Those Directed to the Home
PLMN Country (BOIC-exHC)
Specifications:
3GPP29002, 3GPP22088, 3GPP23088, 3GPP24088
Overview:
When the service is activated, the subscriber cannot make any international call
except calls to the home PLMN country.
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. The service is based
on basic services, including teleservice and bearer service. The MSC implements
the barring of outgoing international calls from the subscriber. The HLR supports


subscribing/withdrawing and activating/deactivating the service. The subscriber
can modify and query the status of the service. Meanwhile, the HLR can specify
whether the right of configuring the BOIC-exHC service is under the control of
the subscriber or the carrier. 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.
Benefits:

benefits.

WHFD-030204
Function name:
Barring of All Incoming Calls (BAIC)
Specifications:
3GPP29002, 3GPP22088, 3GPP23088, 3GPP24088
Overview:
When the service is activated, the subscriber cannot receive any incoming call.
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 subscriber can modify and query the
status of the service in his/her MS. Meanwhile, the HLR can specify whether the
right of configuring the BAIC service is under the control of the subscriber or the
carrier. If the right is under the control of the subscriber, the subscriber can
activate/deactivate the service through the 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.
Benefits:



benefits.


WHFD-030205
Function name:
Barring of Incoming Calls when Roaming Outside the Home PLMN Country
(BIC-ROAM)
Specifications:
3GPP29002, 3GPP22088, 3GPP23088, 3GPP24088
Overview:
If the service is activated, when the subscriber roams outside the home PLMN
country, the subscriber cannot receive any call from other subscribers.
To bar all incoming calls destined to a subscriber roaming outside the home
PLMN country, the HLR activates the basic service groups and stores the code of
the BIC-ROAM service, data of the basic service groups, and the status
information. When the subscriber roams outside the home PLMN country, serves
as the callee and receives a routing request from the caller, the HLR judges
whether the subscriber has activated the BIC-ROAM service. If yes, the HLR
sends an error message to the GMSC, indicating that the callee has barred all
incoming calls.
service. The subscriber can query the status of the service in his/her MS.
Meanwhile, the HLR can specify whether the right of configuring the BIC-
ROAM service is under the control of the subscriber or the carrier. If the right is
under the control of the subscriber, the subscriber can activate/deactivate the
service through the 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.
Benefits:

The service is based on basic service groups. It provides additional way of barring
incoming calls for the carrier, and allows the carrier to provide customized
services.


The service allows subscribers engaged in MS lease business to limit the
incoming call by controlling the call barring function.

WHFD-030300
Function name:
Number Identification Services
The Number Identification Services include

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)

WHFD-030301
Function name:
Calling Line Identification Presentation (CLIP)
Specifications:
3GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
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.
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. When the location of the subscriber changes or after 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 service.
When subscriber A calls subscriber B, the calling number is not displayed in the
MS of subscriber B.
, 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.
Benefits:

The service provides a way for the carrier for attracting more subscribers.

The 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 very 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.

WHFD-030302
Function name:
Calling Line Identification Restriction (CLIR)
Specifications:
3GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
The CLIR service is a supplementary service for the called mobile subscriber.
When a mobile subscriber serves as the caller, the service prohibits the network
from displaying the calling number to the callee.
The HLR stores the CLIR service data for the subscriber. When subscribing the
service, the subscriber can select a restriction mode for the service:
1. Permanent restriction: In this mode, the service is activated for all outgoing
calls. The network does not display the calling number for the callee.
2. Temporary permission: In this mode, the CLIR service is activated only
when the mobile subscriber precedes the called number with #31#.


3. 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 service.
When subscriber A calls subscriber B, the calling number is not displayed in the
MS of subscriber B.
Benefits:

The service can protect the privacy of the subscribers, and help the carrier to
attract more subscribers.

The service can protect the privacy of the subscriber.

WHFD-030303
Function name:
Connected Line Identification Presentation (COLP)
Specifications:
3GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
When a mobile subscriber initiates a call, if the call is forwarded to a third party
subscriber, the network displays the number of the third party subscriber for the
caller.
The HLR stores the COLP data of the subscriber. When the location of the
subscriber changes or after the subscriber modifies data of the service, the HLR
sends the data to the 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.
Benefits:

This service enlarges the number identification scope and increases the business
benefit opportunities.

The service enables the caller to have a clear idea of the call connection status and
have more choices.

WHFD-030304
Function name:
Connected Line Identification Restriction (COLR)
Specifications:
GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
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.
The HLR stores the COLR data of the subscriber. When 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 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.
Benefits:



The 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.

WHFD-030305
Function name:
Override Calling Line Identification Restriction (OVER-CLIR)
Specifications:
GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
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.
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.
Benefits:


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.


WHFD-030306
Function name:
Override Connected Line Identification Restriction (OVER-COLR)
Specifications:
3GPP29002, 3GPP22081, 3GPP23081, 3GPP24081
Overview:
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.
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.
Benefits:


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.

1.2.3 ODB Service
WHFD-040000
Function name:
Operator Determined Barring (ODB)


ODB means that the call barring is under the control of the carrier. The carrier
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 the carrier. The
status of other call restriction supplementary service can be controlled by
either the carrier or the subscriber.

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 the carrier or the subscriber's terminal.
The HLR 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)

WHFD-040100
Function name:
ODB Call Barring
The HLR provides diversified ODB call barring services, allowing the carrier to
manage the subscribers conveniently. The ODB call barring services include:

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)


WHFD-040101
Function name:
ODB: Barring of Outgoing Calls
Specifications:
3GPP29002, 3GPP22041
Overview:
This service can bar all outgoing calls.
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.
Benefits:

The service provides the carrier with an additional way of controlling the
subscribers, and allows the carrier to bar outgoing calls from a defaulting
subscriber and avoid loss in call charge.

The service allows the subscriber to select a conversation mode based on his/her
financial status, and avoids unnecessary waste in call charge.

WHFD-040102
Function name:
ODB: Barring of Outgoing International Calls
Specifications:
3GPP29002, 3GPP22041
Overview:
This service can bar all international outgoing calls.


The MSC realizes barring of international outgoing calls from the subscriber.
Benefits:

subscribers, and allows the carrier to control the call scope of the subscriber and
provide call packages.

The service allows the subscriber to select a conversation mode based on his/her
economic status, and avoids unnecessary waste in call charge.
WHFD-040104
Function name:
ODB- BOCROAM
ODB: Barring of Outgoing Calls when Roaming Outside the Home PLMN
Country
Specifications:
3GPP29002, 3GPP22041
Overview:
The service bars all outgoing calls from a subscriber when the subscriber roams
outside the country of the HPLMN.
When the subscriber roams outside the home PLMN country and initiates a call,
the MSC bars the call from the subscriber.
Benefits:


The service provides the subscriber with an economical conversation mode, and
avoids unnecessary waste in call charge.



WHFD-040105
Function name:
ODB: Barring of Domestic Toll Calls (HPLMN Self-Defined Type 1)
Specifications:
3GPP29002, 3GPP22041
Overview:
This service realizes barring of domestic toll calls (HPLMN self-defined type 1).
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 the carrier 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.
Benefits:


The service provides the subscriber with an economical conversation mode, and
avoids unnecessary waste in call charge.

WHFD-040106
Function name:
ODB: Barring of Incoming Calls (ODB-BAIC)
Specifications:


3GPP29002, 3GPP22041
Overview:
This service realizes barring all incoming calls.
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.
Benefits:


None.

WHFD-040107
Function name:
ODB: Barring of Incoming Calls when Roaming Outside the Home PLMN
Country (ODB-BICROAM)
Specifications:
3GPP29002, 3GPP22041
Overview:
The service bars all incoming calls when a subscriber roams outside the home
PLMN country.
The subscription data of the service is stored in the HLR, but is not sent to the
VLR. The HLR realizes barring 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.
Benefits:



None.

WHFD-040108
Function name:
ODB: Barring of Outgoing Premium Rate Calls (Information)
Specifications:
3GPP29002, 3GPP22041
Overview:
The service realizes barring of outgoing premium rate calls (information).
The MSC realizes barring of outgoing premium rate calls (information).
Benefits:


This service helps subscribers to avoid unnecessary call charges resulting from
ignorance of the call rate of some services.

WHFD-040109
Function name:


Barring of Outgoing Premium Rate Calls (Entertainment)
Specifications:
3GPP29002, 3GPP22041
Overview:
The service realizes barring of outgoing premium rate calls (entertainment).
HLR sends the subscription data of the subscriber to the VLR. The MSC realizes
barring of outgoing premium rate calls (entertainment).
Benefits:


The service can avoid unnecessary loss of call charges due to the ignorance of the
call rate of some services.
WHFD-040200
Function name:
ODB: Barring of Supplementary Services
The HLR supports the ODB: barring of supplementary services, including:
Barring of supplementary services management (WHFD-040201)

WHFD-040201
Function name:
ODB: Barring of Supplementary Services Management
Specifications:
3GPP29002, 3GPP22041
Overview:


The HLR provides supplementary services barring management, and supports
subscribing and withdrawing the service.
The 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.
Benefits:


None.

WHFD-040300
Function name:
ODB: Barring of Roaming
The HLR provides:

ODB: Barring of Roaming Outside the Home PLMN (WHFD-040301)

ODB: Barring of Roaming Outside the Home PLMN Country (WHFD-
040302)

WHFD-040301
Function name:
ODB: Barring of Roaming Outside the Home PLMN
Specifications:
3GPP29002, 3GPP22041


Overview:
The service realizes barring of roaming outside the home PLMN.
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.
Benefits:

The service allows the carrier to control the roaming scope of the subscriber and

The service can avoid unnecessary loss of call charges resulting from roaming.

WHFD-040302
Function name:
ODB: Barring of Roaming Outside the Home PLMN Country
Specifications:
3GPP29002, 3GPP22041
Overview:
The service realizes barring of roaming outside the home PLMN country.
The MSC 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.
Benefits:

The service allows the carrier to control the roaming scope of the subscriber and


The service can avoid unnecessary loss of call charge loss resulting from roaming.

WHFD-040400
Function name:
ODB: Barring of Registration of Forwarded-to Number
Specifications:
3GPP29002, 3GPP22041
Overview:
The service can restrict a subscriber's right of registering the Ftn numbers. It can
bar the registration of:

All Ftn numbers

International Ftn numbers

International Ftn numbers except those destined to the home HPLMN
country
The MSC realizes barring of registration of Ftn numbers. If the subscriber has
subscribed to the service, when the subscriber registers an Ftn number through the
terminal, the registration fails.
The 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 Ftn numbers. 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 Ftn numbers can carry country code.
The HLR can realize these functions through configuration of data or subscription
of the related template. The service allows the carrier to provide different
forwarding policies for different subscriber groups.
Benefits:

The service allows the carrier to control the registration of Ftn numbers and


The service can prevent Ftn registration due to mistaken operations.

WHFD-040500
Function name:
ODB: Barring of Call Transfer
Specifications:
3GPP22041, 3GPP29002
Overview:
This service can restrict a subscriber's call transfer rights.
HLR sends the subscription data of the subscriber to the VLR. The MSC realizes
barring of call transfer on one of the following occasions:

Bar all the call transfers.

Bar call transfer when the served subscriber pays at least one of two calls.

Bar call transfer when the served subscriber pays at least one of two calls at
international call rate.

Bar call transfer when the served subscriber pays at least one of two calls at
regional call rate in.

Bar call transfer when the served subscriber pays at least one of two calls.

Bar call transfer when the served subscribers involved are
under the same MSC/VLR.
Benefits:

The service allows the carrier to control the call transfer and provide various call
packages.

None.


1.2.4 Other Services
WHFD-050000
Function name:
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)

WHFD-050100
Function name:
Liable Subscriber Suspension by Lock
Specifications:
None.
The service provides locking operation, allowing the carrier to suspend the service
of the defaulting subscriber and avoid loss of call charges.
When the carrier 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, the carrier can restrict the subscriber's
services flexibly.
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.


Benefits

The carrier 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.

The timely suspension of services by the carrier can prevent the call charge of the
subscriber from exceeding the limit.
NEs.

WHFD-050200
Function name:
Subscriber Applied Suspension
Specifications:
None.
Overview:
The service allows a subscriber to apply for service suspension.
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.
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 the carrier, 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.
Benefits:

The carrier can provide the lock function for the subscriber.


The subscriber can use the service to reduce unnecessary call charges.
NEs.

WHFD-050300
Function name:
Subscriber Category Setting
Specifications:
3GPP29002, 3GPP23008
Overview:
This service is for defining subscriber category. Every subscriber is allocated with
a subscriber category.
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.
Benefits:

The service allows the carrier to configure various subscriber categories and
divide the subscribers into different groups.

None.

WHFD-571600
Function name:


Multi-NDC
Specifications:
None
Overview:
The multi-NDC service enables a network to have multiple network numbers.
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 the 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.
Benefits:

The service allows the carrier to perform network planning and data configuration
conveniently.

None.
NEs.

1.2.5 Mobility Services
WHFD-060000
Function name:
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)


WHFD-060100
Function name:
Location Management Services
The HLR provides standard protocols compliant location management services,
including:

Location update (WHFD-060101)

Location Cancellation (WHFD-060102)

Purge MS (WHFD-060103)

WHFD-060101
Function name:
Location update
Specifications:
3GPP29002
Overview:
The location update service is a flow initiated by the subscriber's terminal for
maintaining subscriber data consistency between the VLR and the HLR.
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.
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.

Benefits:

This service provides a basic network function.

None.

WHFD-060102
Function name:
Location Cancellation
Specifications:
3GPP29002
Overview:
The service enables the HLR to initiate a flow to clear the subscriber data in the
VLR.
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.
Benefits:


This service provides a basic network function.

None.

WHFD-060103
Function name:
Purge MS
Specifications:
3GPP29002
Overview:
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.
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 1, indicating that
the subscriber is unreachable currently.
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.
Benefits:

This service can reduce traffic volume.

None.



WHFD-060200
Function name:
Authentication Management Services
The HLR provides standard protocols compliant authentication management
services, including

Authentication information provision

Authentication failure report
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 keys, it means that the
MS passes the authentication successfully.

WHFD-060201
Function name:
Authentication Information Provision
Specifications:
3GPP29002
Overview:
The service enables the VLR to initiate a flow to obtain the subscriber
authentication set.
The HLR 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: 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.
The HLR 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.
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 it 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.
If the above two verification events succeed, the MS calculates RES
(RES=f2(RAND)), CK, and IK, and sends RES to the VLR/SGSN. The
VLR/SGSN receives the RES from the MS, and compares the RES with the
XRES of the authentication vector. If they are the same, the authentication
succeeds. Otherwise, the authentication fails.
Benefits:

The service can prevent illegal MS from enjoying telecommunication services and
protect the interests of the carrier.

The 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.

WHFD-060202
Function name:
Authentication failure report
Specifications:
3GPP29002
Overview:


The service enables the VLR to initiate the flow of notifying the HLR of
subscriber authentication failure.
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.
Benefits:

The service allows the carrier to identify and collect statistics on authentication
failure events.

None.

WHFD-060300
Function name:
Subscriber Management Services
The HLR provides standard protocols compliant subscriber management services,
including:

Subscriber Data Insertion(WHFD-060301)

Subscriber Data Deletion(WHFD-060302)

WHFD-060301
Function name:
Subscriber Data Insertion
Specifications:
3GPP29002
Overview:


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.
The HLR 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.
In the data insertion flow, the HLR 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.
Benefits:

This service can ensure the subscriber data consistency between the VLR and the
HLR, and maintain the service availability.

None.

WHFD-060302
Function name:
Subscriber Data Deletion
Specifications:
3GPP29002
Overview:
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.


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.
Benefits:

This service can ensure the subscriber data consistency between the VLR and the
HLR, and maintain the service availability.

None.

WHFD-060400
Function name:
Fault Recovery Services
The HLR provides standard protocols 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)

WHFD-060401
Function name:
HLR Fault Recovery
Specifications:
3GPP29002
Overview:
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.
The HLR 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.
Benefits:

This service has enhanced the network fault recovery capability and ensure the
network data consistency.

None.

WHFD-060402
Function name:
VLR Fault Recovery
Specifications:
3GPP29002
Overview:
When the VLR is faulty and initiates the data recovery flow, the HLR supports
resending subscriber data to the VLR.
When receiving the Restore request from the VLR, the HLR 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.
Benefits:

This service enhances the network fault recovery capability and ensures the
network data consistency.



None.

WHFD-060403
Function name:
Check SS Indication
Specifications:
3GPP29002
Overview:
The HLR supports the flow of notifying the subscriber of the changes to his/her
supplementary services. The service is mainly intended to notify the subscriber of
the possible changes to data of a supplementary service.
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.
Benefits:

This service enhances the network fault recovery capability and network fault
notification fault, and ensures the network data consistency.

The service enables the subscriber to know the changes to a supplementary
service due to network reasons and avoid unnecessary financial losses.

1.2.6 Call Handling Services
WHFD-070000
Function name:
Call Handling Services


The HLR provides standard protocols compliant call processing services,
including:

Send routing information (WHFD-070100)

Provide roaming number (WHFD-070200)
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 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.

HLR
MAP_SEND_ROUTING_INFORMATION
MAP_PROVIDE_ROAMING_NUMBER
MAP_PROVIDE_ROAMING_NUMBERACK
MAP_SEND_ROUNTING_INFORMATIONACK
VLR GMSC

WHFD-070100
Function name:
Send Routing Information
Specifications:
3GPP29002
Overview:
When receiving a request for obtaining routing information, the HLR carries the
routing information in the response message.


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 number 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 number.

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.
The HLR 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.
Benefits:

This service realizes a basic network function.

None.
WHFD-070200
Function name:
Provide Roaming Number
Specifications:
3GPP29002


Overview:
The HLR 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.
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.
Benefits:

This service realizes a basic network function.

None.
1.2.7 Supplementary Service Related Services
WHFD-080000
Function name:
SS-Specific Services
The HLR provides standard protocols 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)

WHFD-080100
Function name:
SS Registration
Specifications:


3GPP29002
Overview:
The HLR enables the subscriber to initiate the registration of a supplementary
service from the terminal.
The HLR 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, the carrier must provide the SS
Registration service in its business hall. The registration of call forwarding related
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 Ftn numbers. Upon receiving the request of registering the Ftn
numbers, the HLR stores these Ftn numbers, and activates the services for the
subscriber. The HLR then sends the subscriber's call forwarding service data to the
VLR.
Benefits:

The service enables the carrier to provide a subscriber-oriented service flow.

The service enables the subscriber to register supplementary services through the
terminal without going to the business hall.

WHFD-080200
Function name:
SS Deletion
Specifications:
3GPP29002
Overview:
The HLR enables the subscriber to deregister a supplementary service from the
terminal.
The HLR enables the subscriber to deregister a supplementary service related to
call forwarding from the terminal. The deregistration of a call forwarding related
supplementary service can be based on basic service groups. For example, the
HLR supports forwarding both a voice call and a data call. Upon receiving the
request of deregistering the call forwarding service, the HLR deletes these Ftn
numbers, and deactivates the service for the subscriber. The HLR then resends the
subscriber's call forwarding service data to the VLR.


Benefits:


The service enables the subscriber to deregister supplementary services through the

WHFD-080300
Function name:
SS Activation
Specifications:
3GPP29002
Overview:
The HLR enables the subscriber to activate a supplementary service from the
terminal.
The HLR 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, the carrier must provide the SS
Activation service in the business hall. The activation of call barring related
supplementary service can be based on basic service groups. For example, the
HLR supports 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.
Benefits:


The service enables the subscriber to activate a supplementary service through the


WHFD-080400
Function name:
SS Deactivation
Specifications:
3GPP29002
Overview:
The HLR enables the subscriber to deactivate supplementary services from the
terminal.
The HLR enables the subscriber to deactivate a call barring supplementary service
from the terminal. The deactivation of a call barring related supplementary service
can be based on basic service groups. For example, the HLR supports 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.
Benefits:


The service enables the subscriber to deactivate a supplementary service through
the terminal without going to the business hall.

WHFD-080500
Function name:
SS Query
Specifications:
3GPP29002
Overview:
The HLR enables the subscriber to query the status of a supplementary service
from the terminal.
The HLR 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.
Benefits:


The service enables the subscriber to query the status of a supplementary service
from the terminal.

WHFD-080600
Function name:
SS Password Registration
Specifications:
3GPP29002, 3GPP22004
Overview:
When a subscriber activates the supplementary service from the terminal, he/she
needs to input the password of the supplementary service. The HLR enables the
subscriber to configure and modify the password of the supplementary service
from the terminal.
The HLR 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.
Benefits:

The service enables the carrier to provide a service security protection mechanism
for the subscriber.

The service can guarantee the security of the subscriber's service.


WHFD-080700
Function name:
SS Password Provision
Specifications:
3GPP29002, 3GPP22004
Overview:
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.
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.
Benefits:

The service enables the carrier to provide a service security protection mechanism
for the subscriber.

The service can guarantee the security of the subscriber's service.

1.2.8 Subscriber Data Management
WHFD-090000
Function name:
Subscriber Data Management
The HLR provides subscriber data management functions, including Subscriber
Definition, Subscriber Deletion, and IMSI Change, and so on. The following
describes these functions.


WHFD-090100
Function name:
Basic Subscriber Data Management
The HLR supports the following basic subscriber data management functions:

Define a single subscriber and define a template subscriber.

Delete a subscriber.

Change the SIM card for a subscriber.

Change the MSISDN number of a subscriber.

Provision/Cancel/Query a basic service.

Provision/Cancel/Register/Delete/Activate/Deactivate/Query a
supplementary service.

Configure and query the ODB parameters of a subscriber.

Query the dynamic data of a subscriber.

WHFD-090101
Function name:
Subscriber Definition
Specifications:
None.
Overview:
The HLR supports defining a single subscriber and a template subscriber.
The HLR supports defining a common subscriber. Meanwhile, the HLR also
supports defining a template subscriber, and provides up to 255 templates.
Regardless of a common subscriber or a template subscriber, the parameters in the
subscription template involve various services, such as call forwarding service,
call barring service, and General Packet Radio Service (GPRS).
Benefits:

The service enables the carrier to provide more convenient subscriber definition
modes.

None.


NEs.
WHFD-090102
Function name:
Subscriber Deletion
Specifications:
None
Overview:
The HLR supports deleting a subscriber.
The HLR supports deleting a subscriber by deleting all data of the subscriber. It
also supports deleting subscribers on batch basis.
Benefits:

The service enables the carrier to provide a basic subscriber deletion function.

None.
NEs.
WHFD-090103
Function name:
IMSI Change
Specifications:
None.
Overview:
The HLR enables a subscriber to change his/her SIM card while keeping the
MSISDN number unchanged.
The HLR supports the IMSI Change service, allowing a subscriber to change
his/her SIM card while keeping the MSISDN number and other subscription data
unchanged


Benefits:

The service enables the carrier to reduce the waste in subscriber number resources,
maintains the stability of the subscribers as a whole, and cultivates the loyalty of
the subscriber.

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.
NEs.
WHFD-090104
Function name:
MSISDN Change
Specifications:
None
Overview:
The HLR enables a subscriber to change his/her MSISDN number without
changing the SIM car.
The HLR supports the MSISDN Change service, allowing a subscriber to change
his/her MSISDN number while keeping the subscription data unchanged
Benefits:

The service enables the carrier to maintain the stability of its subscribers.

Sometimes, a subscriber intends to change his/her MSISDN number out of
privacy reason or other security considerations. The service can well satisfy this
requirement of the subscriber.
NEs.
WHFD-090105
Function name:


Subscriber Number Query
Specifications:
None
Overview:
The HLR supports querying the MSISDN number of a subscriber.
The HLR 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.
Benefits:

The service enhances the subscriber maintenance capability.

None.
NEs.

WHFD-090106
Function name:
Basic Service Setting and Query
Specifications:
None
Overview:
The HLR supports configuring and querying a basic service.
The HLR supports configuring and querying a basic service, including
Teleservices and bearer service (such as voice service and data service).
Benefits:




None.
NEs.

WHFD-090107
Function name:
Dynamic Data Query
Specifications:
None
Overview:
The HLR supports querying a subscriber's dynamic information.
The HLR 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)
Benefits:


None.
NEs.
WHFD-090200
Function name:


Operator Authority Management
Specifications:
None.
Overview:
The HLR supports right/level based subscriber data management.
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.
Benefits:


None.
NEs.

WHFD-090300
Function name:
Dynamic Subscriber Data Management
The HLR supports the following dynamic subscriber data management 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.
WHFD-090301
Function name:
Subscriber Location Modification
Specifications:


None
Overview:
The HLR supports modifying the subscriber location information, including VLR
number, MSC number, and SGSN number.
The HLR 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.
Benefits:


None.
NEs.
WHFD-090302
Function name:
Unsupported Service Replacement
Specifications:
None
Overview:
The HLR uses other supplementary services to replace services not supported by
some network entities, including ODB, AoCC, and CUG.
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.
Benefits:

This service enhances the network compatibility and configurability, and provides
the carrier with additional means of data configuration.

None.


NEs.

WHFD-090400
Function name:
Service Template Setting
Specifications:
None
Overview:
The HLR supports configuring the common service templates (including
subscriber definition template, CAMEL template, and VLR roaming restriction
template) for higher operating efficiency.
The HLR provides a series of templates for the subscription data. These templates
include subscriber definition template and CAMEL template, and can be
referenced repeatedly. The business hall of the carrier can provide some predefined
templates. 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.
Benefits:

This service greatly simplifies service subscription formalities.

None.
NEs.
WHFD-090500
Function name:
Batch Operation
Specifications:
None.
Overview:
The HLR supports batch process functions, including:

Batch process of consecutive number segments

Batch process of non-consecutive number segments


Batch process of files
The HLR 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 HLR also
supports file batch process. You can write all commands to be executed into a file,
and the HLR can execute these commands automatically.
Benefits:

This service simplifies the service subscription procedure and improves operating
efficiency.

None.
NEs.
WHFD-090600
Function name:
Operation Log Management
Specifications:
None
Overview:
The HLR 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. The carrier
can get to know the data operations conducted by an HLR operator.
The HLR 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.
Benefits:

This service provides the carrier with a means of checking and auditing historical
commands.

None.


NEs.

WHFD-090800
Function name:
Subscriber Statistics
Specifications:
None
Overview:
The HLR provides the subscriber statistics function, allowing you to collect
statistics on the total subscribers and total roaming subscribers.
The HLR supports collecting statistics on authentication data records, total
subscribers, and roaming subscribers (for example, subscribers roaming under a
specific VLR). It also supports generating IMSI/MSISDN file list.
Benefits:

This service provides the carrier with a means of collecting statistics.

None.
NEs.

1.2.9 Protocol Interfaces Function
WHFD-100000
Function name:
Protocol Interfaces
The HLR supports MAP protocols and the related interfaces (including C, D, J,
Gc, Gr, and Lh interfaces), as well as the BOSS interface.


WHFD-100100
Function name:
MAP Protocols
Specifications:
3GPP29002
Overview:
The HLR supports MAP Phase 2+ protocol, MAP Phase 2 protocol, and MAP
Phase 1 protocol.
The HLR supports MAP Phase 2+ protocol, MAP Phase 2 protocol, and MAP
Phase 1 protocol. The HLR is forward compatible, and can be upgraded to a
higher version smoothly.
Benefits:

The service provides the carrier with additional service attributes and enables the
smooth network evolution.

None.

WHFD-100101
Function name:
C/D/J/Gc/Gr/Lh Interface
Specifications:
3GPP29002
Overview:
The HLR 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)


Supported protocols: MTP2/MTP3/SCCP/TCAP/MAP
The HLR supports connecting to the interfaces of the surrounding NEs. See the
figure below.
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

Benefits:

The service enables the carrier to satisfy the basic interface requirements.

None.

WHFD-100200
Function name:
BOSS Interface
Specifications:
None.
Overview:


The HLR provides the BOSS interface. Through the BOOS interface, the carrier
can provide subscriber data management interfaces in the business hall, and
realize second system development.
Currently, the HLR supports the BOSS interface adopting the MML command
format.
Benefits:

The service enables the carrier to satisfy the basic interface requirements.

None.

WHFD-100300
Function name:
Application/Data Layer Interface
Specifications:
None.
Overview:
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.
The latest-generation HLR supports the separation of services from data. The
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.
The design of the DS data layer interface has considered the ease in operating the
data, and is irrelevant to the service. The interface supports both HLR application
and CHLR and HSS application.

Provides message based asynchronous access mode. Supports separating
services from data and incorporating multiple operations in a message into a
transaction.


The DS data layer interface is irrelevant to the service flow. Interaction of all
types adopts the request response mode. The DS interface receives request
messages and sends response message.

Enjoys excellent scalability. The newly-added function can be compatible
with the original interface.
Benefits:

The service can satisfy the carrier's requirements for smooth system upgrading and
expansion.

None.
1.2.10 Operation and Maintenance Functions
WHFD-110000
Function name:
Operation and Maintenance Functions
Specifications:
None
Overview:
For the convenience of operation and maintenance, the HLR provides the
following operation and maintenance functions:

Security management

Performance management

Fault management

Configuration management

Device management

Signaling interface tracing

WHFD-110100
Function name:
Security Management
Specifications:


None.
Overview:
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.
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.
1. 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.
2. 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.

3. 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.
G_OPERATOR The administrator-level operator and
operator-level operator have the rights
of the command group.

command names.

command group.
G_USER The administrator-level operator,
operator-level operator, and user-level
operator have rights of the command
group.

command names.

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.

command names.

command group.
G_0G_9 The Admin, administrator-level
operator, and NMS operator have all
rights of the command group. The
custom-level operator has all or
partial rights of the command group.

command names.

command group.
G_10_31 The Admin, administrator-level
operator, and NMS operator have all
rights of the command group. The
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.

The figure below shows the relationship between different command groups.


G_OPERATOR
G_USER
G_GUEST
G_ADMIN

4. 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.

5. 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.

Benefits:

The service provides a perfect system right control mechanism. The carrier can
control the access of the system by both workstations and operators, making daily
operation and maintenance very flexible and safe.

None.


NEs.

WHFD-110200
Function name
Performance Management
Specifications:
None.
Overview:
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 HLR 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.
The table below lists the measurement items supported by the HLR.
Measurement category Measurement items
Global component
measurement
CPU occupancy measurement
CPU measurement
MAP measurement
SUB measurement
3GSCS measurement
3GSWB measurement
3GSWC measurement
3GSWCS measurement
3GSWG measurement
3GSWL measurement
WCDMA HDU
measurement
3GSWLK measurement


3GSWO measurement
3GSWOS measurement
3GSWR measurement
2GSWG measurement
2GSWC measurement
2GSCS measurement
2GSWCS measurement
2GSWL measurement
2GSWLK measurement
2GSWO measurement
2GSWOS measurement
2GSWR 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
Signaling and interface
measurement
TCAP messages count


TCAP utilization rate measurement

Benefits:

The service enables the carrier to implement various traffic measurement tasks,
monitor the running status of the equipment, and optimize the network.

None.
NEs.
WHFD-110300
Function name:
Fault Management
Specifications:
None
Overview:
The HLR 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.
The HLR 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 HLR provides the following powerful alarm management functions.
1. You can query alarm information at any time, and specify the alarm level,
alarm type, alarm time for an alarm to facilitate alarm query.
2. For the convenience of comprehension, every alarm contains a piece of
explanatory information.
3. You can enable/disable alarm shielding manually.
4. The HLR provides an alarm box. When an alarm is reported, the alarm box
generates siren to remind the maintenance personnel.
Benefits:


The service enables the carrier to get to know the problems in the HLR, and take
preventive measures accordingly.

None.
NEs.
WHFD-110400
Function name:
Configuration Management
Specifications:
None
Overview:
The HLR provides configuration management function, allowing you to configure
the system, a board, and an interface.
The HLR provides flexible data configuration functions, allowing you to
configure data online and offline. Meanwhile, the HLR supports configuring the
data through the MML. You can produce data configuration scripts conveniently,
thus reducing configuration difficulties.
Benefits:

The service enables the carrier to configure the data of the HLR flexibly and
satisfy various data configuration requirements.

None.
NEs.
WHFD-110500
Function name:
Equipment Management
Specifications:


None
Overview:
The HLR provides equipment management function, allowing you to manage the
software and hardware of the equipment conveniently.
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
Benefits:

The service enables the carrier to manage the HLR conveniently and satisfy the
daily operation requirements.

None.
NEs.
WHFD-110600
Function name:
Signaling Tracing
Specifications:
None
Overview:
The HLR provides powerful signaling tracing functions, including interface
signaling tracing and subscriber interface signaling tracing.
WHFD-110601
Function name:


Interface Signaling Tracing
Specifications:
None
Overview:
The service enables you to trace the signaling of the SCCP/MTP/MAP interface,
and save the tracing results in a file.
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.
Benefits:

The service enables the carrier 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.

None.
NEs.
WHFD-110602
Function name:
Subscriber Signaling Tracing
Specifications:
None.
Overview:
The 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.


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.
Benefits:

The service enables the carrier to find causes of the problems in the services of a
subscriber.

None.
NEs.
1.2.11 Reliability Functions
WHFD-120000
Function name:
Reliability Functions
Specifications:
None.
Overview:
The reliability design of the HLR involves hardware reliability design and
software reliability design.
WHFD-120100
Function name:
Hardware Reliability
Specifications:
None
Overview:
The hardware reliability design of the HLR includes redundancy & backup design
and power supply reliability design.
WHFD-120101
Function name:


Redundancy and Backup Design
Specifications:
None
Overview:
The HLR adopts redundancy & backup design. It adopts redundancy design for
key components. In the databases, it adopts perfect backup mechanism to ensure
the security of the subscriber data.
The HLR adopts the following redundancy & backup technologies:

Adopts system-level multi-processors and step-by-step processing
technology.

Adopts hot backup for hardware of important boards.

Adopts dual-network dual-plane (V9: multi-node cluster) technology for the
databases to realize real-time data backup and avoid single-point fault.
Benefits:

The service can enhance the system reliability and ensure uninterrupted service
provisioning.

None.
NEs.
WHFD-120102
Function name:
Power Reliability
Specifications:
None
Overview:
Faults in the power supply may result in a disaster. The HLR adopts high-
reliability design for the power supply system.
The HLR 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.

Benefits:

The service enables the carrier to enhance the system reliability, ensure
uninterrupted service provisioning, and improve the customer's satisfaction level.

None.
NEs.
WHFD-120200
Function name:
Software Reliability
Specifications:
None
Overview:
The HLR adopts the following high-reliability designs for its software:

Automatic fault detection and self-healing capability

Automatic switchover or manual switchover

Subscriber data automatic/multi-level backup

Flow control

System restoration upon upgrade failure

WHFD-120201
Function name:
Automatic Fault Detection and Self-Healing
Specifications:
None


Overview:
The HLR adopts real-time fault monitoring and self-healing designs to ensure the
reliability of its software.
The HLR 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 automatic switchover if the fault cannot be removed. The
backup system takes over the tasks of the faulty hardware and software,
without affecting the services.
Benefits:


None.
NEs.
WHFD-120202
Function name:
Automatic/Manual Switchover
Specifications:
None.
Overview:
When the active system of the HLR is faulty, the HLR can automatically switch to
the standby system. The HLR supports both automatic switchover and manual
switchover.
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.
The HLR database unit of V6 consists of two hosts. When the active host is faulty
and the fault cannot be removed, the HLR switches to the standby host
automatically. Adopting redundancy design, the HLR enjoys high reliability, and
ensures the interests of the carrier. On some special occasions (such as network
upgrading), you switch from the active system to the standby system manually.


The ATCA boards of V9 version work in load-sharing mode, and do not involve
switchover.
Benefits:


None.
NEs.
WHFD-120203
Function name:
Subscriber Data Automatic/Multi-Level Backup
Specifications:
None.
Overview:
A core function of the HLR is to store a large quantity of subscriber data, which
are very important to the carrier. The HLR provides automatic/multi-level backup
mechanism to ensure the security of the subscriber data. When accidents take
place, the subscriber data can be recovered immediately.
The HLR adopts the following measures to ensure the security of important data:
1. Automatic backup:
The HLR supports automatic backup of important subscriber data and information
at a specified time.
(V6)
2. Multi-level backup mechanism

Back up data to other area of the same disk.

Back up the data to the disk array.

Back up data to an external magnetic tape.
The HLR ensures the reliability of the data through multi-level backup
mechanism.
3. Manual data backup. You can back up the data at any time.
(V9)
4. The HLR provides powerful 3-level data backup and recovery functions.
Every function is applied in different occasion and has effectively protected
the security of the system.

Duplicate the IMDB data in the master node and the slave node under the
same cluster.


Back up the IMDB data from a node of the cluster to the local disk through
snapshot duplication.

Back up data in the IMDB of the master node to the physical database
DBMS to realize data synchronization.
Accordingly, there are three means to realize the data recovery:

Recover the data by duplicating data from the master node.

Recover data from the snapshot file in the local disk.

Recover data from the physical database.
Benefits:

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.

None.
NEs.
WHFD-120204
Function name:
Flow Control
Specifications:
None
Overview:
The HLR provides the flow control function. When the traffics 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.
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.
Adopting perfect traffic control design, the HLR9820 can effectively process burst
heavy traffics.
5. Applies multi-level traffic control to the C/D/J/Gr/Gc interface to realize
smooth traffic volume adjustment.


6. Detects and checks the payload handling efficiency and resource utilization
rate of the processor in real-time to realize auto-adapted flow control.
7. Allows flexible configuration of flow control parameters to realize forced
flow control.
8. 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.
Benefits:
The service enables the carrier to enhance the system reliability, avoid service
interruption resulting from heavy burst traffics, and prevent the avalanche effect.
None.
NEs.
WHFD-120205
Function name:
System Restoration Upon Upgrade Failure
Specifications:
None
Overview:
When upgrading fails due to exceptions, the HLR supports quick rollback to the
original version. This can prevent the upgrading failure from affecting the services
too long.
To prevent upgrading failure, the HLR 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.
Benefits:

The service provides the carrier with an assurance measure against upgrading
failure. Once the upgrading fails, the service can rollback the subscriber data and
version to the initial status to protect the system against the failure.

None.


NEs.
1.2.12 Authentication Functions
WHFD-130000
Function name:
Authentication Functions
Specifications:
3GPP29002
Overview:
The authentication function is defined according to a protocol, and is
accomplished by the Authentication Centre (AUC). Incorporating the AUC
function, the HLR supports 2G and 3GPP standard authentication flows and the
respective authentication encryption algorithms.
WHFD-571400
Function name:
Quintuplet to Triplet Conversion
Specifications:
3GPP29002, 3GPP33102
Overview:
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.
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 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.
Benefits:

The 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 the carrier in the 2G network.

The service allows a 3G subscriber to roam to a 2G network and ensures smooth
and safe voice conversation.
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.
WHFD-571500
Function name:
KI Encrypted KI
Specifications:
None
Overview:
The HLR uses K4 as the key, and encrypts/decrypts KI data through the DES
algorithm. The subscriber can select different K4 for encrypting the KI. The HLR
stores the encrypted KI data in its database.
The HLR supports the encrypted KI data. Out of consideration of security, the KI
data is encrypted during its transfer from the card manufacturer to the carrier. The
HLR 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 supported encryption algorithm is the DES algorithm.
Benefits:

The service can protect the security of the KI data. A person cannot obtain the real
KI data even though he can access the HLR database. Therefore, the service can
prevent theft of cards.

None.
NEs.
WHFD-571501
Function name:
DES Algorithm


Specifications:
None
Overview:
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.
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. It allocates
every 64 bits to a group, and adopts standard arithmetic and logical operations.
The HLR uses K4 as the key, and encrypts/decrypts KI data through the DES
algorithm.
Benefits:

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.

None.
NEs.
WHFD-571000
Function name:
COMP128-1 Algorithm
Specifications:
3GPP29002
Overview:
The HLR supports the COMP128-1 algorithm.
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.
Benefits:



The service provides basic authentication algorithm to satisfy basic network
authentication requirements.

None.
WHFD-571100
Function name:
COMP128-2 Algorithm
Specifications:
3GPP29002
Overview:
algorithm.
encrypted channels.
Benefits:

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.

None.
WHFD-571200
Function name:
COMP128-3 Algorithm
Specifications:
3GPP29002


Overview:
algorithm.
encrypted channels.
Benefits:

Compared with COMP128-2, the COMP128-3 algorithm can better protect the
security of authentication security.

None.
WHFD-571300
Function name:
Milenage Algorithm
Specifications:
3GPP29002, 3GPP35205, 3GPP35206
Overview:
The HLR supports the 3G Milenage authentication algorithm.
The Milenage authentication algorithm is a 3G network authentication algorithm.
The USIM card supports the Milenage authentication algorithm only.
Benefits:

The service can satisfy the requirements of 3G MS/network for authentication
algorithms.

None.


WHFD-571400
Function name:
G-Milenage Algorithm
Specifications:
3GPP29002, 3GPP35205, 3GPP35206
Overview:
The HLR supports the G-Milenage authentication algorithm. The G-Milenage
algorithm is the Milenage algorithm applied in the GSM network.
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.
Benefits:

The service can satisfy the requirements of 2G MS/network for authentication
algorithms. It supports multiple authentication algorithms.

None.

1.2.13 CS Data Services
WHFD-510000
Function name:
CS Data Services
Specifications:
3GPP29002
Overview:
The HLR 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.
1. FAX service


The HLR supports two types of FAX services:

Voice + G3 FAX (TS 61) service

Automatic G3 FAX (TS 62) service
2. Data CDA service

Asynchronous duplex circuit data service working at 300bit/s (BS21),
1200bit/s (BS22), 1200/75bit/s (BS23), 2400bit/s (BS24), 4800bit/s (BS25),
and 9600bit/s (BS26)

Transparent/Non-transparent 3.1 kHz audio VF/UDI data service
3. 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).
4. 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).
5. Data PDS service
Packet access, synchronous, UDI, non-transparent PDS service working at 2.4k
bits/s (BS51), 4.8k bits/s (BS52), and 9.6k bits/s (BS53).
6. Voice and data alternation service
The HLR supports voice and data alternation service (BS61).
7. Voice + data service
The HLR supports the data service that consists of voice service + data service
(BS81).
8. UMTS bearer service
The HLR supports asynchronous bearer service (BS20) and synchronous bearer
service (BS30).
Benefits:

The service enables the carrier to provide diversified data services, satisfy the
requirements of telecommunication markets, and boost its competitiveness.

The service enables the subscriber to subscribe to the data service and obtain
various information resources.
1.2.14 GPRS Services
WHFD-520000
Function name:
GPRS Services


Specifications:
3GPP29002, 3GPP22060, 3GPP23060, 3GPP29061
Overview:
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 GPRS service accomplishes packet data functions through additional
functional entities (GGSN and SGSN) deployed in the GSM network. The
additional functional entities comprise the GSM-GPRS network.
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 HLR 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 over an interface.
The GPRS is mainly applied to realize E-mail service, WWW browsing, WAP
service, e-commerce, information query, and remote monitor.
The HLR allows the subscriber to subscribe to the network access modes of GSM
and GPRS, or both of them.
The HLR GPRS service supports:

Flexible billing for the GPRS service

QoS of the GPRS (Ext-QOS)

Dynamic PDP address

Static PDP address (IPv4, IPv6, and X.25)

GPRS MO/MT short message service

Restriction of GPRS subscriber from accessing the GPS network
In comparison to the 2.5G GPRS, the UMTS GPRS supports the expanded QoS
attribute and the PDP accounting attributes, and provides more powerful and
excellent network services.
Benefits:

The service enables the carrier to realize the network functions of the GSM,
GPRS, and UMTS through the HLR, thus saving the investment of the carrier.



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.
The HLR realizes the function in compliance with the standard protocol in
cooperation with the GGSN/SGSN. But there is no special requirement for these
NEs.
1.2.15 Supplementary Services
WHFD-030000
Function name:
Supplementary Services
Specifications:
3GPP29002
Overview:
The following introduces the supplementary services of the optional functions,
including:
1. Call Waiting/Call Hold (CW/CH)
2. Multi Party (MPTY)
3. Unstructured Supplementary Service Data (USSD)
4. Closed User Group (CUG)
WHFD-030400
Function name:
Call Waiting/Call Hold (CW/CH)
Specifications:
3GPP29002, 3GPP22083, 3GPP23083, 3GPP24083
Overview:
The CW service allows a mobile subscriber in conversation status to establish a
call connection to another incoming call. The CW service allows a mobile
subscriber to suspend the current conversation and receive another incoming call.
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 only when they are applied 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.
Benefits:

The service can enhance the service provisioning capability of the carrier, and
attract the more subscribers. Meanwhile, the service can improve call completion
rate, and improve traffic volume.

The 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.
WHFD-030500
Function name:
Multi Party (MPTY)
Specifications:
3GPP29002, 3GPP22084, 3GPP23084, 3GPP24084
Overview:
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).
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 a
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.
Before subscribing to the MPTY service, the subscriber must have subscribed to
the CH service.
Benefits:

attract the more subscribers. It provides a simple telephone meeting solution for
the business subscriber.

The service allows multiple subscribers to talk with each other. The service allows
the business subscriber to hold a simple telephone meeting.
WHFD-030600
Function name:
Unstructured Supplementary Service Data (USSD)
Specifications:
3GPP29002, 3GPP24090
Overview:
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.
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 HLR supports USSD service of version 1 and version 2.
Benefits:

The service enables the carrier to provide many value-added services, such as
information on stock exchange, lottery, weather forecast, and air freights, thus
attracting more subscribers.


The service can satisfy the subscriber's requirements for information in many
aspects, such as lottery information and stock exchange.
The HLR realizes the function in compliance with the standard protocol. The
HLR must cooperate with the SCP (or the USSD center) and the VMSC.
WHFD-030700
Function name:
Closed User Group (CUG)
Specifications:
3GPP29002, 3GPP22085, 3GPP23085, 3GPP24085
Overview:
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.
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.
Benefits:



attract the enterprise subscribers.

The subscribers within the CGU can enjoy flexible call rates.
cooperate with the MSC/VLR. But there is no special requirement for the
MSC/VLR.
1.2.16 CAMEL Services
WHFD-530000
Function name:
Customized Applications for Mobile network Enhanced Logic (CAMEL)
Services
Specifications:
3GPP29002, 3GPP22078, 3GPP23078, 3GPP29078
Overview:
The 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. The carrier 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 CAMEL attribute, the carrier 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:
1. CAMEL phase 1:
2. CAMEL phase 2:
3. CAMEL phase 3:
4. CAMEL phase 4
In the four phases, the CAMEL has different application scopes:
5. CAMEL phase 1: The CAMEL attribute is applied to services related to
MO/MT calls.
6. CAMEL phase 2: The CAMEL attribute is applied to services related to the
utilization of supplementation services.
7. CAMEL Phase 3: The CAMEL attribute is applied in SMS MO, GPRS
sessions, PDP context, HLR subscriber data control, and network signaling
traffics.
8. 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 HLR supports the four CAMEL versions.


WHFD-530100
Function name:
CAMEL Phase 2 Services
Specifications:
3GPP29002, 3GPP23078
Overview:
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.
The HLR supports the following CAMEL related functions:

Supports J 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:
1. O-CSI (WHFD-530101)
2. T-CSI (WHFD-530102)
3. SS-CSI (WHFD-530103)
4. TIF-CSI (WHFD-530104)
5. U-CSI (WHFD-530105)
6. UG-CSI (WHFD-530106)
Benefits:
7. Benefits for the carrier:
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 the carrier to add new services and new attributes more
flexibly and conveniently. Meanwhile, the carrier can utilize the attributes of the
exiting IN network (familiarity number, pre-payment, and message station
service), and reduce the subsequent investment in equipment.
8. Benefits for the subscriber:
The subscriber can enjoy various IN services provided by the HLR, for example,
familiarity number, message station service, and advice of charge.


WHFD-530200
Function name:
Specifications:
3GPP29002, 3GPP23078
Overview:
The HLR supports CAMEL Phase 3 service.
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)
Benefits:

The CAMEL service enables the subscriber to subscribe to the IN service
immediately. Utilizing the flexible service configuration methods of the IN
network, the CAMEL service allows the carrier to add new services and new
attributes more flexibly and conveniently. Meanwhile, the carrier can utilize the
attributes of the IN network (familiarity number, pre-payment, and message
station service), and reduce the subsequent investment in equipment.

WHFD-530300
Function name:


Specifications:
3GPP29002, 3GPP29078
Overview:
The HLR support CAMEL Phase 4 service.
In addition to the attributes of CAMEL Phase 3, CAMEL Phase 4 service supports:
1. MO-SMS-CSI (WHFD-530301)
2. MT-SMS-CSI (WHFD-530302)
Benefits:

The CAMEL service enables the subscriber to subscribe to the IN service
immediately. Utilizing the flexible service configuration methods of the IN
network, the CAMEL service allows the carrier to add new services and new
attributes more flexibly and conveniently. Meanwhile, the carrier can utilize the
attributes of the IN network (familiarity number, pre-payment, and message
station service), and reduce the subsequent investment in equipment.


1.2.17 Location Services (LCS)
WHFD-540000
Function name:
Location Services (LCS)
Specifications:
3GPP22071, 3GPP23171, 3GPP24030, 3GPP25305, 3GPP25923, GPP29002
Overview:
The LCS service is a GSM standard compliant service. It functions independently
from any basic service.
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. The carrier can provide the LCS service by deploying
several LCS functional entities, without too many changes to the network.
The HLR supports subscribing to the LCS service in Universal, Call related, Non-
call related, or PLMN operator mode. The HLR 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.
Benefits:

With the development of the telecommunication market, the provisioning of the
LCS service is inevitable. The carrier should provide the LCS service as soon as
possible to satisfy the requirements of the market and enhance its service
competitiveness.

The LCS allows a subscriber to know his/her current location, and brings about
great convenience to the daily life.
The HLR realizes the function in compliance with the standard protocol. It must
cooperate with the GMLC, SMLC, MSC, and SGSN.

1.2.18 Other Services
WHFD-050000
Function name:
Other Services
Specifications:
None
Overview:
Other services include:

CFD (WHFD-050600)

CFNRy Default Time Medication (WHFD-050800)

WHFD-050600
Function name:
Call Forwarding Default (CFD)
Specifications:
None.
Overview:


The HLR provides the CFD service independently, without cooperation with the
MSC/VLR.
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 the carrier.
If a subscriber's basic service based CFD 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 number 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:
1. The subscriber has not subscribed to the conditional call forwarding
supplementary service.
2. The subscriber has not registered the supplementary service.
3. The subscriber has not activated the supplementary service.
For example, subscriber A has registered and activated the CFD service; the
subscriber's Ftn number 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.
Benefits:
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 number (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 number for every conditional call forwarding service.
The CFD service enables the carrier to provide powerful and flexible call
forwarding function for the subscriber and enhance its competitiveness.
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
number (such as the voice mail box) specified by the CFD service.
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 on the
MSC/VLR.


WHFD-050800
Function name:
CFNRy Default Time Modification
Specifications:
None
Overview:
The HLR supports the CFNRy Default Time Modification.
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 HLR provides an interface for
modifying the default time. The default no reply time can be 5s, 10s, 15s, 20s, 25s,
or 30s.
Benefits:

The carrier 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.

The service enables the subscriber to configure the no replay time of call
forwarding for his/her own CFNRy service.

WHFD-050900
Function name:
Automatic Device Detection (ADD)
Specifications:
3GPP29002
Overview:
The HLR provides the ADD function. The ADD function allows the related
configuration data to be automatically sent to the user equipment (UE) when the
core network detects the change of the IMEISV, IMSI, or subscription data.
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.)
In addition, 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 a message to the ADD server. The
ADD server then updates the configuration data of the UE through the network.
Benefits:

The ADD function simplifies the operations of the subscribers who use the data
services, and thus increases the customer satisfaction.

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.
Requirement for other NEs:
The ADD function is implemented by the HLR and the ADD server together. In
addition, a proprietary interface, namely the SOAP interface, is required between
the HLR and the ADD server.

1.2.19 Mobility Services
WHFD-060000
Function name:
Mobility Services
Specifications:
3GPP29002
Overview:
The mobility services include the Subscriber Information Services (WHFD-
060500).

WHFD-060500
Function name:
Subscriber Information Services
Specifications:
3GPP29002
Overview:


The subscriber information service:
1. Supports querying the subscriber's information at any time.
2. Provides the subscriber's information.
WHFD-060501
Function name:
Any Time Interrogation
Specifications:
3GPP29002
Overview:
The Any time interrogation is a standard protocol compliant subscriber
information service.
The SCP can initiate a request for obtaining a subscriber's location information
and status information to the HLR.
Benefits:

The service enables the carrier to adopt the call charge rate based on the location
to which a subscriber roams, and boost its competitiveness.

The subscriber can benefit from the call charges.
cooperate with the MSC/VLR and the SCP. But there is no special requirement for
MSC/VLR.
WHFD-060502
Function name:
Subscriber Information Provision
Specifications:
3GPP29002
Overview:
The Subscriber Information Provision service is a standard compliant subscriber
information service.
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.
Benefits:



The service enables the carrier to obtain detailed subscriber's location and status
information to provide more powerful functions. For example, the carrier can
adopt the call charge rates based on the cell to which a subscriber roams, and
boost its competitiveness.

The subscriber can benefit greatly from the call charges or enjoy better network
service.
1.2.20 Subscriber Data Management
WHFD-090000
Function name:
Subscriber Data Management
Specifications:
None
Overview:
The subscriber data management function involves:

Scheduled Batch Operation Execution (WHFD-090700)

Subscriber Data Export to Text File (WHFD-090900)

Subscriber Data Import from Test File (WHFD-091000)

3G Subscriber Data Storage (WHFD-091100)

WHFD-090700
Function name:
Scheduled Batch Operation Execution
Specifications:
None
Overview:
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.
The carrier can perform the batch operations at the time other than peak traffic
hours, and avoid the inconvenience brought about by manual batch operations.
Benefits:


The carrier can conduct batch operations more flexibly.

None.
NEs.
WHFD-090900
Function name:
Subscriber Data Export to Text File
Specifications:
None
Overview:
Huawei's HLR supports exporting all or partial subscriber data to a text file.
Huawei's HLR supports exporting all or partial subscriber data to a text file. The
text file complies with standard subscriber data format of Huawei's HLR. You can
analyze, convert, and collect statistics on the exported subscriber data.
Benefits:

The service enables the carrier to export the data in the HLR database to a text file
and process the exported data conveniently.

None.
NEs.
WHFD-091000
Function name:
Subscriber Data Import from Test File
Specifications:
None
Overview:
Huawei's HLR supports importing subscriber data from a text file with subscriber
data of standard format.


Huawei's HLR supports importing subscriber data from a text file with subscriber
data of standard format. The service enables the carrier to import the subscriber
data from one HLR to another.
Benefits:

The service enables the carrier to transfer subscriber data exported from an HLR's
database. For example, the carrier can transfer a portion of subscriber data in an
HLR to another. Besides, when taking over the HLR of other vendor, the carrier
can convert the data of the HLR of other vendor into a text file with data
complying with Huawei's standard subscriber data format, and then import the
subscriber data into the database of Huawei's HLR.

None.
NEs.
WHFD-091100
Function name:
3G Subscriber Data Storage
Specifications:
3GPP29002, 3GPP23008
Overview:
Huawei's HLR supports storing and identifying 3G subscriber data.
Huawei's HLR 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.
Benefits:

The service enables the carrier to provide diversified customized 3G services.

The subscriber can enjoy the benefits bought about by 3G service.


1.2.21 Networking Functions
WHFD-560000
Function name:
Networking Functions
Specifications:
3GPP29002
Overview:
The networking functions include:

Multi-SP (WHFD-560100)

TDM 2M Signaling Link (WHFD-560200)

MAP phase2+ (WHFD-560500)

SIGTRAN (WHFD-560300)

WHFD-560100
Function name:
Multi-SP
Specifications:
None
Overview:
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.
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.
Benefits:



The 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.

None.
NEs.
WHFD-560200
Function name:
TDM 2M Signaling Link
Specifications:
None
Overview:
Huawei's HLR supports TDM 2M links.
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.
Benefits:

The application of 2M link in signaling points with large signaling traffics in
between can reduce cost and simplify networking. Besides, if the HLR does not
support Multi-SP function, it is subject to the limitation of 16 links. If the 16 64K
links cannot satisfy the traffic volume requirements, the adoption of 2M links can
well satisfy the traffic requirements.

None.
NEs.

WHFD-560500
Function name:
MAP phase2+
Specifications:


3GPP29002
Overview:
Huawei's HLR supports the MAP phase2+.
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.
Benefits:

The HLR supports MAP phase2+. As a result, the carrier can provide services that
are based on the MAP phase2+, and increase its revenue.

The subscriber can enjoy services that are based on MAP phase2+.

WHFD-560300
Function name:
SIGTRAN
Specifications:
None
Overview:
Huawei's HLR supports the SIGTRAN, namely IP networking.
The HLR 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.
Note:
The SIGTRAN service does not include the M2UA function.


Benefits:

The HLR supports independent IP networking and can help the carrier to save
investment in SG construction. The HLR 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.

None.
NEs. If the peer end adopts TDM for bearing No. 7 signaling, a signaling gateway
must be adopted for signaling conversion.
WHFD-560600
Function name:
SCTP multi-homing
Specifications:
RFC2960
Overview:
In IP networking, the HLR provides the SCTP multi-homing function, which
improves the reliability of the IP network.
In IP networking, the HLR 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.
Benefits:

The reliability of the IP network is improved.

None
Requirement for other NEs:
The HLR implements the SCTP multi-homing function in compliance with the
standard protocol. 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.

1.2.22 Enhanced Functions
WHFD-570000
Function name:
Enhanced Functions
Specifications:
3GPP29002
Overview:
The enhanced functions include: some special services, such as multi-MSISDN
function, hot billing, voice ring back tone service, and voice broadcast service.

WHFD-570100
Function name:
VLR Regional Roaming Restriction
Specifications:
None
Overview:
The VLR Regional Roaming Restriction service is based on VLR/SGSN roaming
list. Every subscriber has his/her own VLR/SGSN roaming list.
The VLR Regional Roaming Restriction service enables the carrier to provide
various roaming restriction services flexibly. Without deploying any extra network
equipment, the carrier 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, the carrier 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 the carrier.
The VLR Regional Roaming Restriction service is widely applied in local
communication services. The carrier compiles 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).
To provide the VLR Regional Roaming Restriction service, the carrier 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.
Benefits:

The service enables the carrier to provide local communication network service
for the subscribers or provide roaming restriction services for the subscribers
individually, thus improving its competitiveness.

The subscriber who has subscribed to the service can enjoy relatively low charge
rate and save the expense. If the carrier provides the roaming restriction service
individually, the subscriber can specify the roaming area for himself/herself.
NEs.
WHFD-570700
Function name:
CAMEL Restriction
Specifications:
None
Overview:
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.


The HLR supports the CAMEL Restriction service. The carrier can configure the
service in the HLR to control whether it should send CAMEL data in a flow.
The following lists the major CAMEL restriction solutions:
1. 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.
2. 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.
3. 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.
4. 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 the carriers. For
example, according to the basic service keys, the carrier 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.
Benefits:

The service enables the carrier to configure the subscriber-based CAMEL
processing capability in the HLR. The carrier can provide more customized
CAMEL services for the subscriber, and enhance its competitiveness.

None.
NEs.


WHFD-570701
Function name:
TCSI Suppression Enhancement
Specifications:
None
Overview:
The HLR supports the TCSI Suppression Enhancement function. The carrier can
configure the service to decide whether the HLR should send the subscriber TCSI
data.
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.
Benefits:

The service enables the carrier to configure the subscriber-based CAMEL
processing schemes in the HLR. The carrier can provide more customized
CAMEL services, and enhance its competitiveness.

None.
NEs.

WHFD-570900
Function name:
Multi-MSISDN
Specifications:
3GPP29002
Overview:
The HLR allows an IMSI subscriber to subscribe to multiple MSISDN numbers.
The HLR 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).
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.
Benefits:

The service enables the carrier to attract more subscribers and improve its market
competitiveness.

The subscriber of the service can use different MSISDN numbers for different
services.
WHFD-571300
Function name:
Multi-OP
Specifications:
None
Overview:
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 HLR supports allocating multiple OPs
for a carrier.
OP is a parameter of the UMTS authentication. Through the parameter, the carrier
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.
Benefits:

The service allows different USIM cards to use different OPs, greatly enhancing
the security of the system.

Every subscriber can have his/her own OP. Consequently, the security of the
USIM card is further improved.
NEs.
WHFD-571700
Function name:


Hot Billing
Specifications:
None
Overview:
The HLR provides the Hot Billing service for the subscriber. The service belongs
to the carrier's self-defined supplementary service.
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.
Benefits:

The carrier can provide real-time billing service for the subscriber, for example,
telephone lease service.

The subscriber can obtain the call bill in real-time. The subscriber can enjoy real-
time billing services.
The service is of non-standard service. The HLR must cooperate with Huawei's
MSC/VLR.
WHFD-571800
Function name:
Alternative Line Service (ALS)
Specifications:
3GPP29002
Overview:
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.
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.
Benefits:

The service can attract more subscribers for the carrier and improve the
competitiveness of the carrier.

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.
WHFD-572000
Function name:
HLR-Specific Roaming Restriction
Specifications:
None
Overview:
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.
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.
Benefits:

The HLR-Specific Roaming Restriction service is of HLR level, and is effective
to all subscribers. It provides a flexible roaming restriction function for the carrier.


None.
NEs.
WHFD-572100
Function name:
SMC Address Filtering
Specifications:
None
Overview:
The HLR supports filtering messages from the short message center according to
an address list.
You can configure an address list in the HLR. The HLR 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.
Benefits:

This service can avoid malicious attacks through short messages and alleviate the
payload of the HLR and the network.

None.
NEs.
WHFD-572101
Function name:
SCP Address Filtering
Specifications:
None
Overview:
The HLR supports the SCP address filtering function.
You can configure an SCP address list in the HLR. The HLR can apply the
address list to shield A short messages from the SCP. This mechanism can avoid
malicious attacks, and alleviate the payload of the HLR and the network.
Benefits:


This service can avoid malicious attacks through short messages and alleviate the
payload of the HLR and the network.

None.
NEs.
WHFD-572200
Function name:
CF-Specific Black and White Lists
Specifications:
None
Overview:
The CF-Specific Black and White Lists service enables the HLR to control the
subscriber's registration of the call forwarding service. The service is effective to all
subscribers. You can configure a global table with call forwarding rules for the
specified Ftn numbers in the HLR. Through the global table, the HLR can control
whether a subscriber can register the Ftn numbers.
The CF-Specific Black and White Lists in the HLR exist in the form of a global
table. The global table is effective to all subscribers. The carrier can compile Ftn
number segments (including the start Ftn number and the end Ftn number)
according to the actual circumstances, and configure the call forwarding rule and
the default call forwarding rule based on the number segments. When the Ftn
numbers registered by a subscriber fall within the number segments, the HLR
applies 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 Ftn numbers, the registration fails.
Benefits:

The service enables the carrier to manage the subscriber's call forwarding more
flexibly, and prevent the registration of illegal numbers.

This service prevents the subscriber from incurring financial loss resulting from
registration of illegal Ftn numbers.
NEs.
WHFD-572300
Function name:


Network Capability Configuration (NCC)
Specifications:
None
Overview:
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.
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:
1. 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.
2. 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.
3. 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
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.
4. 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.
5. 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.
Benefits:

The service can improve the HLR's compatibility with the surrounding NEs,
increase the HLR's MAP operation success rate and efficiency, satisfy the carrier's
customized network compatibility requirements and facilitate the carrier's network
deployment.

None.
The HLR realizes the functions internally. There is no special requirement for
external NEs.
WHFD-572400
Function name:
Ring Back Tone
Specifications:
None
Overview:
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.


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.
Benefits:

The service can provide extra revenue for the carrier and improve the subscriber's
satisfaction level.

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.
The service is of non-standard service. The HLR must cooperate with the
MSC/VLR.

WHFD-573000
Function name:
Local Mobile Station Identity (LMSI)
Specifications:
None.
Overview:
The HLR supports the LMSI service. The service is designed especially for some
special areas. Some services are provisioned in cooperation with the satellite
mobile telecommunication system. The HLR provides the LMSI function to
facilitate the provisioning of these services.
The following describes the basic processing flow of the function:
The HLR transfers Location Area Code (LAC) over the LMSI cells.
1. In the location update flow, the VLR sends the subscriber's LAC to the HLR.
2. The HLR stores the received LMSI cells without any processing.
3. When the HLR initiates the PRN request, it sends the LMSI cells to the VLR.
Through the function of the HLR, the carrier can provide services in some special
areas under the help of the satellite mobile telecommunication system.
Benefits:



The service enables the carrier to provide services in special areas under the help
of the satellite mobile telecommunication system, enlarge the service coverage,
and enhance its competitiveness.

None.
The service is of a non-standard service. The HLR must cooperate with the
MSC/VLR to realize the service.
WHFD-573100
Function name:
Zone Code
Specifications:
3GPP29002
Overview:
The HLR 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.
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 the carrier through the Zone Code service. A roaming area can have up
to 10 zone codes.
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.
Benefits:

The service enables the carrier to provide local communication network service
for the subscribers or provide roaming restriction services for the subscribers
individually, thus improving its competitiveness.

The subscriber who has subscribed to the service can enjoy relatively low charge
rate and save the expense. If the carrier provides the roaming restriction service
individually, the subscriber can specify the roaming area for himself/herself.
cooperation with the MSC/VLR/SGSN. But there is special requirement.


WHFD-573200
Function name:
Access Restriction Data (ARD)
Specifications:
3GPP29002
Overview:
The ARD service enables the carrier to restrict the GSM subscriber's accessing the
UMTS network.
The HLR 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. The carrier 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 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.
Benefits:

The service enables the carrier to control 2G subscribers' access to the UMTS
network, and reasonably arrange and open the network resources for the
subscribers.

The service enables the subscriber to access the desired wireless network.
MSC/VLR.
WHFD-573300
Function name:
CS Allocation/Retention Priority (CARP)
Specifications:
3GPP29002
Overview:
The CARP service enables the carrier 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.


The CARP service divides the subscriber's priorities into three levels: high
(category-1 subscriber), medium (category-2 subscriber), and low (category-3
subscriber). The carrier 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.
Benefits:

The service enables the carrier to allocate different priorities to different
subscribers and provide voice service of different QoS for these subscribers
accordingly. The service also enables the carrier to provide QoS solutions for the
subscribers flexibly. When the network is congested, the carrier 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.

The service ensures that the high-end subscriber can enjoy better voice and data
services.
The HLR realizes the function in compliance with the standard protocol CARP
and must cooperate with the MSC/VLR. But there is no special requirement for
the MSC/VLR.
WHFD-573301
Function name:
Allocation/Retention Priority (ARP)
Specifications:
3GPP29002
Overview:
The ARP service enables the carrier 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.
The ARP service divides the subscriber's priorities into three levels: high
(category-1 subscriber), medium (category-2 subscriber), and low (category-3
subscriber). The carrier 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.
Benefits:

The service enables the carrier to allocate different priorities to different
subscribers and provide voice service of different QoS for these subscribers
accordingly. The service also enables the carrier to provide QoS solutions for the
subscribers flexibly. When the network is congested, the carrier 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.

The service ensures that the high-end subscriber can enjoy better voice and data
services.
The HLR realizes the function in compliance with the standard protocol ARP in
cooperation with the SGSN/GGSN. But there is no special requirement for these
NEs.
WHFD-573400
Function name:
Support of Optimal Routing (SOR)
Specifications:
3GPP23079
Overview:
The SOR service is a network attribute. It allows a call to be routed to the actual
location of the callee to reduce the circuits occupied unnecessarily. The SOR
service is suitable to inter-country roaming and inter-network roaming. It can
reduce the call charge of the caller and the callee and promote the international
roaming service.
The SOR is an attribute that complies with standard protocols such as 02.79,
03.79, and 23.078.The SOR is a network attribute. It enables a call to be routed to
the current location of the callee or to the Ftn number directly without passing
through the callee's HPLMN or VPLMN.
The caller's HPLMN decides whether to optimize the routes according to the
information provided by the callee's HPLMN. The HPLMN can decide whether to
optimize routes of a call for some special subscribers.
The purpose of the SOR is to reduce unnecessary inter-network call connections.
Benefits:


The SOR service is suitable to inter-country roaming and inter-network roaming.
It can reduce the call charge of the caller and the callee and promote the
international roaming service.

The service can help the subscriber to save international roaming charge.
MSC/VLR.
WHFD-574000
Function name:
Global Tracing
Specifications:
3GPP29002
Overview:
To remove faults in the increasingly-complicated 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.
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 HLR 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.
Benefits:

The service enables the maintenance personnel to pinpoint a fault in a network to
a specific NE, and then remove the fault. The carrier can improve the fault
handling efficiency.

None.


WHFD-574200
Function name:
Service Change and UDI Fallback Function
Specifications:
3GPP23172, 3GPP23018
Overview:
The HLR supports the Service Change and UDI Fallback Function service.
The HLR 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:
1. The callee's MS does not support the VP call.
2. The callee is unwilling to receive the call in VP mode.
3. The callee has not subscribed to the VP service.
4. The callee has roamed to the GSM network.
5. During the VP call process, the caller or callee is switched to the GSM
network.
Benefits:

The 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.

The 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.
WHFD-574500
Function name:
CLIP by HLR
Specifications:
None.
Overview:


The 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.
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:
1. The GMSC carriers the calling number in the SRI request message.
2. HLR sends the PRN request with the calling number in private coding
Benefits:

The 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.

None.
The service is of non-standard service. The HLR must cooperate with the
MSC/VLR to realize the service.
WHFD-574800
Function name:
USSD Barring
Specifications:
None.
Overview:
The HLR supports barring the USSD operations.
The HLR enables the carrier 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 the carrier 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.
For example, the carrier provides 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.


Benefits:

The service enhances the carrier's control over the subscriber's behaviors, and
ensures the interests of the carrier.

None.
NEs.

WHFD-574900
Function name:
2G/3G QoS Mapping
Specifications:
None
Overview:
The HLR supports the 2G/3G QoS mapping.
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.
Benefits:

The service enhances the network's compatibility.

None.
NEs.

1.2.23 GSMR Functions
WHFD-572600
Function name:
GSMR functions
Overview:
The HLR supports the following GSMR functions:


1. Voice Broadcast Service (VBS) (WHFD-572700)
2. Voice Group Call Service (VGCS) (WHFD-572800)
3. Enhanced Multi-Level Precedence and Pre-Emption (eMLPP) (WHFD-
572900)
4. Follow Me (WHFD-573800)
5. User-to-User Signaling (UUS) service (WHFD-573900)

WHFD-572700
Function name:
VBS
Specifications:
3GPP29002
Overview:
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.
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:
1. 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.
2. 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 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.
Benefits:

Benefits for the carrier
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.

The service enables the subscriber to make unidirectional conversation.

WHFD-572800
Function name:
Voice Group Call Service (VGCS)
Specifications:
3GPP29002
Overview:
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.
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 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:
1. 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.
2. 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.
Benefits:

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.

The service enables the subscriber to realize multi-party conversation (half
duplex).

WHFD-572900
Function name:
Enhanced Multi-Level Precedence and Pre-Emption (eMLPP)
Specifications:
3GPP22067, 3GPP23067, 3GPP24067
Overview:
The eMLPP service enables 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 the carrier to maximize its benefits.
The eMLPP service is a supplementary service, and complies with GSM02.67,
GSM03.67, and GSM04.67 protocols. The 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, the carrier
provides differentiated services for the subscribers, and enables 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 the carrier, 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.
Benefits:

The service allows the carrier to provide differentiated services for subscriber
groups of different levels. When the network resources are scarce, the service can
help the carrier to maximize its benefits.



The service enables subscribers of different eMLPP priorities to enjoy
differentiated services.
cooperation with the MSC/VLR/BSC/RNC/MS/UE. But there is no special
requirement for these NEs.

WHFD-573800
Function name:
Follow Me (FM)
Specifications:
3GPP22094, 3GPP23094
Overview:
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 MSISDN under the follow-me function number, and associate the follow-
me function number with the real subscribers.
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's 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.
3. 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.
4. 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.
5. Initial number
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.
6. 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.
7. 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.
8. 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.
Benefits:

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.

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.



WHFD-573900
Function name:
User-to-User Signaling (UUS)
Specifications:
3GPP29002, 3GPP22087, 3GPP23087, 3GPP24087
Overview:
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.
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:
9. 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 signalings. 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.

10. 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.
11. 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.
Benefits:

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.

Under the GSMR system, the subscriber can realize transfer of follow-me
function numbers, confirmation of high-priority calls, and accurate addressing.

1.2.24 Redundancy Functions
WHFD-570403
Function name:
Redundancy Functions
Overview:
The HLR supports the following redundancy functions:
1. 1+1 Load-Sharing Redundancy (WHFD-570401)
2. 1+1 Mated Redundancy (WHFD-570402)
3. N+1 Mated Redundancy (WHFD-570501)
4. N+1 Compatibility Redundancy (WHFD-570502)
5. Seamless Geography Redundancy (WHFD-010300)

WHFD-570401
Function name:
1+1 Load-Sharing Redundancy
Specifications:
None.


Overview:
The HLR9820 supports 1+1 Load-Sharing Redundancy solution.
The 1+1 Load-Sharing Redundancy solution is a real-time hot backup solution.
The HLRs for mutual backup share the same HLR9820 version. The two HLRs
serve as mutual backup, and process their respective services, and are in the status
of taking over another HLR.
Benefits:

The service can greatly improve the network availability. When one HLR
becomes faulty, the other HLR takes over all services immediately.
Advantages: The two HLRs operate simultaneously, and save the investment in
the network.

None.
It is required to configure data in the STP/MSC and establish connections to the
redundant HLR.

WHFD-570402
Function name:
1+1 Mated Redundancy
Specifications:
None.
Overview:
The HLR9820 supports the 1+1 Mated Redundancy solution.
The 1+1 Mated Redundancy solution is a real-time hot backup solution. The
active and standby HLRs share the same HLR9820 version. The active HLR
processes all services; the standby HLR is ready to take over the services of the
active HLR.
Benefits:

The service can greatly improve the network availability. When the active HLR
becomes faulty, the other HLR takes over all services immediately. When the
active HLR is faulty, the subscriber can still enjoy various network services.
Advantage: Once the standby HLR takes over the services of the active HLR, the
capacity of the standby HLR is large enough. Besides, the daily maintenance of
the standby HLR does not affect the normal running of the active HLR.

None.


It is required to configure the corresponding data in the STP/MSC, and establish
connections between the STP/MSC and the redundant HLR.
WHFD-570501
Function name:
N+1 Mated Redundancy
Specifications:
None.
Overview:
The HLR9820 supports N+1 Mated Redundancy solution.
The N+1 Mated Redundancy solution adopts Huawei's HLR9820 of the same version
as the active and standby HLRs. The redundant HLR provides service backup for
N active HLRs. The active HLR processes the services. The redundant HLR is
ready to take over the services of the active HLR.In this solution, the redundant
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
redundant HLR.
Benefits:

Advantage: Multiple HLRs share an HLR disaster center, saving the subscriber's
investment.

None.
WHFD-570502
Function name:
N+1 Compatibility Redundancy
Specifications:
None.
Overview:
The HLR9820 supports the N+1 Compatibility Redundancy solution.
In the N+1 Compatibility Redundancy solution, the active HLR can be the HLR
of various vendors. There is only one redundant HLR, which can take over the
services of N active HLRs. The active HLR processes the services; the redundant


HLR is ready to take over the services of the active HLR. In this solution, the
redundant 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 redundant HLR.
Benefits:

Advantages: Multiple HLRs share an HLR disaster center, saving the subscriber's
investment.

None.

WHFD-010300
Function name:
Seamless Geography Redundancy
Specifications:
None.
Overview:
The HLR supports self-backup. In the overall system of the HLR, the data nodes
are presented to the service nodes as a whole. Due to the separation of the data
from services, the redundancy solution is only implemented in the data layer. The
variation in the service layer does not affect the implementation of the redundancy
solution in the data layer. Compared with traditional HLR service layer
redundancy solutions, this solution enjoys many advantages. In the traditional
HLR, if it is necessary to modify the service logics, the synchronization
configurations of the redundant HLR must be modified accordingly. For example,
in the process of synchronizing the dynamic data, if the MAP configurations are
modified or added, you must modify the logic module used for private commands
conversion The redundancy function is closely associated to the service
processing. This brings about tremendous inconvenience to the realization of the
redundancy function.
The data node redundancy solution supports self-redundancy. In other words, the
data nodes realize self-redundancy without deploying independent redundant
HLR as required in the traditional HLR redundancy solution.
For the convenience of illustration, the following describes a data layer 1+2
redundancy solution. See the figure below.


In the above figure, sites 1, 2, and 3 are the active sites. No site serves as the
standby one, because the data nodes realize the redundancy internally. The service
node does not have to figure out which DSU in which cluster provides service for
itself. It only needs to send a request to the data layer.
In the data layer, the data nodes are deployed in the form of cluster. A cluster
contains three nodes: one master node and two slave nodes. The three nodes have
the same data. The master node processes its own data and synchronizes its data
to the slave nodes in other sites.
In a cluster, as long as one node is normally available, the services of the cluster
remain normal. When the master node is faulty, the system automatically elects a
new master node from the two slave nodes, and then switches the services to the
new master node within milliseconds to ensure uninterrupted service provisioning
to the service layer. During the system running process, the master node is
dynamic. Besides, the system supports automatic fault isolation. A faulty node in
the cluster is not allowed to participate in the election of new master node until it
recovers from the fault and broadcasts the recovery information to other nodes.
The data layer is divided into two parts: routing module DRU and data storage
module DSU. The data deployment and synchronization mechanism complies
with the above description.
Benefits:



The HLR in data layer redundancy solution is a self-redundancy system. The
networking of the HLR in this solution is different from that of the HLR in
traditional redundancy solution. Every data site is the active one and has backup
data. In the traditional HLR redundancy solution, an independent redundant HLR
must be deployed. In comparison, the data layer redundancy solution has much
higher equipment utilization rate. The HLR self-redundancy solution adopts mesh
topology, with data distributed in different nodes. Its data reliability and security
is far higher than that of the traditional redundancy solution. Due to its high
utilization rate and high reliability, the data layer redundancy solution can reduce
the carrier's CAPEX and OPEX, and enhance the carrier's comprehensive
competitiveness.

None.
NEs.

1.3 Additional Function Description
WHFD-030800
Function name:
Explicit Call Transfer (ECT) service
Specifications:
3GPP23091
Overview:
The ECT function allows a subscriber to transfer an incoming/outgoing call to a
third party and then exit the conversation.
Before subscription of the ECT service, the subscriber must have subscribed to
the call hold service.
The ECT service also allows a subscriber to connect two calls (A-B call and A-C
call) into a call between two parties (B-C call), and then exit the call.
The A-B/A-C call can be either an incoming call or an outgoing call. Before the
call transfer, the A-B call connection must have been established. The A-C call
connection may have been established, or subscriber C is in ringing status.
Subscriber A has subscribed to the ECT service. When subscriber A has to handle
two calls with subscriber B and subscriber C simultaneously (each of the two calls


can be either an incoming call or an outgoing call), he/she can establish a call
connection between subscriber B and subscriber C, and then exit from the call
connection between subscriber B and subscriber C.
Before the call transfer, the A-B call connection must have been established. The
A-C call connection may have been or may have not been established. The
network equipment decides whether the ECT function is supported. If the network
equipment supports the ECT, it notifies subscriber C of the call transfer.
The subscriber's terminal can enable the ECT through a menu or the USSD
operation.
Benefits:
Provide the ECT service as a supplementary service, satisfy the subscriber's
requirement for the service, and boost the revenue of the carrier.
The subscriber can conveniently establish a call connection between other two
parties and exit the call connection.
The HLR realizes the function in compliance with the standard protocol by
cooperating with the MSC and VLR. There is no special requirement on these
NEs.
WHFD-040600
Function name:
ODB PS
Specifications:
3GPP29002
Overview:
With the ODB PS function, the carrier can limit the subscriber's access to the
Barring of Packet Oriented Services.
The ODB PS function can limit the rights of a subscriber in using services of the
packet service (PS) domain.
1. Disable the barring of the packet services
2. Enable the barring of all packet services.
3. Enable the barring of packet service when the access point is in the HPLMN
and the subscriber roams in the VPLMN.
4. Enable the barring of packet service when the access point is in the VPLMN
and the subscriber roams in the VPLMN.


Benefits:
Through the function, you can make all packet services inaccessible to a
defaulting subscriber, bar the subscriber from using the Packet Oriented Services.
When an accident takes place, a subscriber can bar all packet services through the
carrier to prevent further loss.
When working with the SGSN/GGSN, the HLR realizes the function through the
standard protocol. There is no special requirement on SGSN/GGSN.
WHFD-050400
Function name:
Automatic prefix addition for IP calls
Specifications:
None
Overview:
When a subscriber dials a toll call, the service can automatically precede the toll
call number with an IP number specified by the carrier (such as 17951 and 17911).
Through the service, the subscriber does not have to add an IP number before the
toll call number, and the system can automatically convert the dialup mode into IP
phone call dialup mode.
The service applicant is generally a mobile service subscriber. The carrier can
specify the prefix of the IP call. Consequently, the subscriber can initiate an IP call
without dialing the IP prefix. The toll call will be charged according to the rate of
a toll call.
A subscriber of the service can also make a local call. But the call is not routed
over the IP telephone network. The routes of other calls are the same as that of the
IP call with the dialed number consisting of the IP prefix and called number.
Benefits:
The service can make the dialup of an IP phone call very convenient, thus
attracting more subscribers to make IP toll calls.
The subscriber can make an IP toll call without dialing the IP prefix.


The service is a non-standard service. The implementation of the service requires
the cooperation between the HLR and Huawei MSC/VLR.
WHFD-050500
Function name:
North American Equal Access (NAEA)
Specifications:
3GPP29002
Overview:
The NAEA service allows the subscriber to select a desired long-distance network.
When the subscriber's terminal is powered on, it specifies a long-distance network
as the default long-distance network. When making a toll call, the subscriber can
use the long-distance network. You can modify the long-distance network carrier
information for the mobile subscriber.
When making a toll call, a subscriber needs to select a desired long-distance
network carrier. A mobile carrier may capitalize on its advantages in access
network to force the subscriber to select its own long-distance network. The
NAEA service is intended to avoid unequal competition in the selection of long-
distance network carrier. The mobile carrier must provide a function that allows
the subscribers themselves to select desired long-distance network carriers and
realizes equality in accessing the long-distance networks. The service is
implemented according to standard protocols.
To ensure equality in long-distance network access, every toll call service carrier
is allocated a carrier ID code (CIC). The subscriber specifies a toll call service
carrier at the time of subscription. After a subscriber signs an agreement with a
toll call service carrier, the subscriber can select the long-distance network of the
carrier by dialing the CIC of the carrier. The service supports two application
modes: preset CIC and CIC dialing.
The HLR supports configuring the preset network selection attribute, which
realizes equal network access. When the location of an MS is updated, the HLR
sends the information on the preset network selection attribute of equal access to
the VLR.
Benefits
The service allows the subscriber to freely select the desired long-distance
network carrier, and promote fair competition among long-distance network
carriers. It can bring about many benefits to the long-distance network carrier,
thus attracting more customers for the mobile carrier.
This service allows a subscriber to select a desired toll call service carrier
according to his/her own preference, call rate, and network coverage.


When working with the MSC/VLR, the HLR realizes the function through the
standard protocol. There is no special requirement on MSC/VLR.
WHFD-050700
Function name:
Barring of all Outgoing calls when Roaming Outside HPLMN-country (BORO)
Specifications:
None
Overview:
When a subscriber of the service roams outside HPLMN-country, the service bars
all outgoing calls.
When a subscriber roams within the HPLMN-country, the activated BORO
service has no impact on the subscriber. When the subscriber roams outside the
HPLMN-country, the activated BORO, similar to the activated BAOC service,
bars all outgoing calls of the subscriber.
The BORO service is not a standard supplementary service. There is no allocated
supplementary service code for it. The subscription, registration, and
deregistration operations for the service can only be accomplished by the operator.
Benefits
Through the BORO service, the carrier can conveniently bar all outgoing calls
from a subscriber.
None
Requirements for other NEs
The HLR realizes the function internally. There is no special requirement on the
external NE.

WHFD-550100
Function name:
Advice of Charge Information supplementary service and Advice of Charge
Charging supplementary service (AoCI & AoCC)
Specifications:
GSM0204 3GPP29002


Overview:
There are two types of charge information notification supplementary services:

AoCI service

AoCC service
The AoCI service realizes real-time call charge display. After a subscriber
registers the AoCI service, the network equipment sends Charge Advice
Information (CAI) to the subscriber. The MS can calculate the call charge
automatically according to the CAI. The subscriber can display the charge of a
call by selecting a menu item, and total up the call charges. If the Visited PLMN
(VPLMN) does not support the AoCI service, the MS that has subscribed to the
AoCI service can initiate a phone call, but cannot calculate call charge. The
settlement of the charge of the AOCI service is carried out by the network
equipment. The mobile subscriber can only obtain the charge information of a call.
Besides all functions of AOCI, the AoCC service also supports totaling up the call
charges, and saving the result in the SIM/USIM. If the total call charge reaches
the maximum value specified in the SIM/USIM, the service bars all outgoing calls
(except the emergency call) and free incoming calls. The service is not targeted at
the subscriber of the service, but the user of the MS specified by the subscriber of
the service. After a call finishes, the user of the MS pays the call charge for the
subscriber of the service. The charge of the AOCC service is settled in the MS.
The MSC sends call rate information to the MS. The MS must support Phase2
standards. The SIM card dedicated for the service must be made available. If the
VPLMN does not support the AoCC service, it refuses the request for updating
location information from an MS that has subscribed to the AoCC service, making
the MS unable to make any call (except the emergency call). This service is
applicable to the business of leasing SIM/USIM card. The person who rents the
SIM/USIM card pays the call charge to the holder of the SIM/USIM card
according to the call charge records; the holder of the SIM/USIM card settles the
call charge with the carrier.
Benefits:
The charge information notification service enables the provisioning of more
services, such as MS lease and real-time call charge display. Consequently, the
carrier can attract more subscribers and enhance its competitive edge.
By subscribing the charge information notification supplementary services, the
subscriber can establish charging related business. For example, the subscriber
can lease its MS to others and collect rent according to the call charges. When a
subscriber is in business journey, the subscriber can purchase a temporary card.
The card can only be used for one time and is not rechargeable. The subscriber
does not need to pay the subscription fee and number fee. The MS cannot roam or
can only roam within a province. The call charge calculation is made at the MS,
and the network equipment cannot provide information on the account balance of
the MS. Therefore, the temporary card can avoid high expense in roaming.


The terminal must support the service.
WHFD-570600
Function name:
Call Forwarding Announcement Suppression
Specifications:
None
Overview:
The HLR supports enabling/disabling the call forwarding announcement
suppression function for some special forwarded-to numbers (Ftn). When a call is
to be forwarded to one of these Ftns, the system plays announcement or
suppresses announcement playing for the caller.
The function is of system-level function, with priority higher than that of call
forwarding configuration selected by the subscriber at the time of service
subscription.
The call forwarding supplementary service contains the subscription item: call
forwarding announcement. The options for configuring the subscription item
include "yes" and "no". The subscription item is provided for a type of call
forwarding service, and is a part of the subscription data of the subscriber. The
subscription item must be configured when a subscriber subscribes to the call
forwarding service. Provided that the subscription item has been configured for
subscriber B, and subscriber B has registered a call forwarding service, which
allows a call for subscriber B to be forwarded to subscriber C. When subscriber A
calls subscriber B and the call forwarding mechanism is triggered, subscriber A
hears a prompt tone, indicating that the call is forwarded. If the subscription item
is not configured, subscriber A cannot hear the prompt tone. The parameter is
configured on the basis of an individual subscriber.
The Call Forwarding Announcement Suppression attribute belongs to system data,
is configured especially for an Ftn, and is effective to all call forwarding services.
The options for configuring the Call Forwarding Announcement Suppression
attribute include "yes" and "no". The priority of system data is higher than that of
the subscriber's subscription data. For example, the Call Forwarding
Announcement Suppression attribute is enabled for the number 90099. When a
call to a subscriber is forwarded to the number, the caller cannot hear the prompt
tone. The Call Forwarding Announcement Suppression function is implemented
by the HLR independently. You can configure and query the call forwarding
announcement suppression data in the HLR. The HLR sends the Call Forwarding
Announcement flag to the VLR and the GMSC.
Benefits:


The service provides additional functions for call forwarding services, and allows
the carrier to control call forwarding announcement.
None.
external NE.
WHFD-570800
Function name:
Origin for Forwarded-to Number Analysis (OFA)
Specifications:
None
Overview:
The function controls the range of Ftns through a subscriber's subscription
template.
The function of the OFA is similar to that of the prohibited Ftn table in the global
table. But the prohibited Ftn table takes effects globally, and is effective to all
subscribers.
In the HLR, the basic mechanism of the OFA service is to define OFA templates.
The OFA template specifies the numbers to which a call can be forwarded, and the
numbers to which a call is prohibited to be forwarded. For example, a subscriber
fills in an OFA template when registering a call forwarding service. When
registering the Ftns, the HLR compares these Ftns with prefixes in the OFA
template. If the Ftns match the prefixes in the OFA template, these Ftns can be
processed according to the rules defined in the template. The OFA template also
supports a default forwarding rule, which decides whether an Ftn not matching
any prefix can be registered. When subscribing a call forwarding service (CFU,
CFB, CFNRy, and CFNRc), a subscriber can fill in an OFA template. The ID of an
OFA template is specified when the subscriber subscribes to the call forwarding
service. The contents of an OFA template are defined by the operator. The ID of
an OFA template is unique. The OFA function is realized by the HLR
independently.
Benefits:
This function allows the carrier to manage the call forwarding service flexibly,
and to prevent the subscriber from registering illegal numbers.


Through the function, the subscriber can limit the range of Ftns, and avoid
forwarding a call to an undesired number due to operation error.
external NE.
WHFD-571900
Function name:
Voice & Videophone Dual Number (VVDN)
Specifications:
3GPP29002
Overview:
The HLR allows a subscriber to adopt different numbers for the video call and the
voice call.
The VVDN service allows a subscriber to adopt different numbers for voice calls
and videophone calls. The caller ID display is based on the call type. When a
subscriber initiates a voice call, the MS of the callee displays the voice call
number of the subscriber; if the subscriber initiates a video call, the MS of the
callee displays the video call number of the subscriber.
Benefits
The VVDN service helps to attract subscribers with special requirements, and to
boost the competitiveness of the carrier.
The VVDN service allows a subscriber to adopt different numbers for voice calls
and videophone calls.
Requirements for other NEs
When working with the MSC/VLR, the HLR realizes the function through the
standard protocol. There is no special requirement on the MSC/VLR.

WHFD-560400
Function name:
ATM 2M
Specifications:
None


Overview:
Huawei's HLR supports ATM 2M links.
The HLR9820 supports providing ATM bearer through E1 reverse multiplexing
(also ATM 2M).The protocol stack is MTP3B/SAAL/ATM/E1. The upper layer
protocol supports the transmission of the MAP signaling.
Benefits:
This function can provide flexible networking solutions for the carrier, and allows
the carrier to utilize the existing equipment and transmission resources and reduce
the construction cost.
None.
The peer end NE must share the same network interface.
WHFD-010000
Function name:
HLR Distributed Deployment
Overview:
The HLR of the latest generation adopts the distributed architecture and supports
detached networking. Logically, the architecture of the HLR is divided into four
layers: protocol access layer, service processing layer, data service layer, and data
storage layer. The data processing and service processing are implemented in
different layers. Refer to the figure blow:


The protocol access layer and the service processing layer are integrated into the
front end (FE) for processing signaling and service logics. The data service layer
and the data storage layer are integrated into the back end (BE) for storing and
managing data and providing data service for the upper layer.
The logic function is deployed in a physical entity. That is, the data node and the
service node can be deployed either as an integrated entity or separately.
WHFD-010100
Function name:
Front End Distributed Deployment
Specifications:
None.
Overview:
The HLR consists of service nodes and data nodes. An HLR may contain multiple
service nodes. These service nodes can be deployed as a physical entity (unified
deployment) or separately (distributed deployment). In the unified deployment,
the service nodes operate in the same physical entity; in distributed deployment,
the service nodes operate in different physical entities. The service nodes work in
load sharing mode. When a service node is faulty, other service nodes take over
the task of the service node to ensure the normal operation of the system. When
the distributed deployment is adopted for the service nodes, the service nodes can
be distributed geologically. When the service nodes intend to communicate with
an NE, the system establishes a connection between the NE and the nearest
service node.


The service nodes of the HLR mainly accomplish the processing of signaling and
service logics. The service nodes deployed in different locations are disaster
tolerant, and work in load sharing mode. The figure below shows a deployment
mode.

The service nodes of the HLR include two modules:

Signaling Access Unit (SAU)

Service Control Function (SCF)
The SAU works in load sharing mode, and sends services to the SCF modules
according to the dialogue number of the TCAP and the load sharing principle. The
SCF module also works in load sharing mode, and distributes data requests to


DRU modules. The figure below shows the internal modules of the service node.

Benefits:
Separation of services from data enables the service node to concentrate on
signaling access and service processing. It also brings convenience and flexibility
to the carrier. In the case of distributed deployment, requests from the local MSC
are sent to the local service node directly, without forwarding by the STP.
Working in load sharing mode, the service nodes have greatly enhanced the
network reliability. When the network capacity is insufficient, you can expand the
network capacity by adding service nodes to the network.
None.
external NE.

WHFD-010200
Function name:
Back End Distributed Deployment
Specifications:
None.
Overview:
The HLR consists of service nodes and data nodes. An HLR may contain multiple
service nodes. These service nodes can be deployed as a physical entity (unified
deployment) or separately (distributed deployment). In the unified deployment,
the service nodes operate in the same physical entity; in distributed deployment,
the service nodes operate in different physical entities. The data nodes can be
deployed in different locations. Each node stores all subscriber data. The
subscriber data in these nodes are well synchronized. In this way, the data nodes
become disaster tolerant. The data node stores the subscriber data of the service
nodes, and allows the service node to add, delete, update, and query data.


The data nodes of the HLR are:

Service Management Function (SMF)

Data Request Unit (DRU)

Data Service Unit (DSU)

Service Management Unit (SMU)
The SMF manages the subscriber data, and works in load sharing mode. The SMF
node 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.
The DRU node queries the routing table according to the key (IMSI or ISDN) in
the requests from the SCF and the SMF, and forwards the data requests to the
DSU. The DRU works in load sharing mode. Each DRU contains all routing data.
The DRU distributes the data requests to DSU clusters according to the routing
information.
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.
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 dual-host mode.
The data node is also referred to as the back end (BE). 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 active/standby load sharing mode. The figure below
shows the deployment of data nodes.


DRU
cluster
DSU
cluster 1
DSU
cluster 2
DSU
cluster 3
SMF cluster SMF cluster SMF cluster
Service node 1 Service node 2
Data node 1
Data node 2 Data node 3
DRU master DRU slave
DRU slave
DSU master DSU slave DSU slave
DSU master DSU slave
DSU slave
DSU master
DSU Slave DSU slave

Benefits:
The data node supports distributed deployment. The data nodes are disaster
tolerable, greatly increasing the data security. Meanwhile, the data node is
deployed separately from the service node. The disaster in the data nodes does not
affect the service data. Therefore, the carrier can maintain the network
conveniently and flexibly. The data management adopts the load sharing mode.
When a node becomes faulty, it does not affect the running of the whole system,
greatly improving the system reliability.


None.
The HLR is integrated with the function. There is no special requirement on the
external NE.
1.4 Virtual HLR Function
WHFD-570200
Function name:
Virtual HLR function
Overview:
When the HLR provides services for subscribers in multiple areas, multiple
virtual HLRs can be defined in a physical HLR, with each virtual HLR
corresponding to an area. Through the virtual HLR function, the maintenance
personnel in an area can only maintain the information of the subscribers of the
corresponding area. Meanwhile, the virtual HLR function allows the maintenance
personnel to collect statistics on the subscribers and the utilized services in every
area and to improve the operability. Presumably, the HLRs are deployed in areas
with sparse mobile subscriber distribution in line with the traditional HLR
deployment solution, and an HLR is deployed in each area. Consequently, the
capacity of each HLR cannot be put into full play.
For the purpose of saving investment, the virtual HLR technology can be
employed to store the data of the subscribers in these areas in a physical HLR in a
centralized way, and divide the physical HLR into multiple virtual HLRs logically.
Through right allocation, different maintenance personnel handle the subscriber
data in the virtual HLR of different area.
Additionally, the new-generation HLR is carrier-class large-capacity HLR. It
adopts the virtual HLR technology to facilitate the management of carriers and
facilitate business operation.
In the actual business operation, you can configure the upper limit of the
subscriber quantity in every virtual HLR and adjust the capacity of every virtual
HLR. Every virtual HLR is configured with a subscriber template to provide
differentiated service.
WHFD-570300
Function name:
Number Segment-Based Virtual HLR
Specifications:
None.
Overview:
Huawei's HLR supports the number segment based virtual HLR.


The HLR supports defining the virtual HLRs based on number segments.
Different operator has different allocated IMSI/MSISDN number segment. Only
the authorized operator can handle the subscriber data of a specified number
segment. The carrier can allocate a number segment to an area, and define the
operators for the HLR. The operator maintains a virtual HLR as if the virtual HLR
is an independent HLR. Actually, these virtual HLRs are maintained in a unified
manner.
Benefits:

The service enables the carrier to deploy a physical HLR for multiple areas for
saving investment. Meanwhile, the operation of an area can operate the virtual
HLR conveniently as if the virtual HLR is a real HLR. The system operability is
very high.

None.
NEs.
WHFD-570400
Function name:
HLRSN-Based Virtual HLR
Specifications:
None.
Overview:
The HLR supports defining the virtual HLR based on HLR Serial Number
(HLRSN). The HLRSN is the unique identifier of every virtual HLR.
The HLR uses the HLRSNs to identify the data of different carriers, and allocates
the HLRSNs to different operators. An operator can only handle the subscriber
data of the allocated HLRSN. The division of global data and template data is
based on the HLRSN. Since every virtual HLR supports the HLRSN attribute, the
subscriber data, global data, template data, and authentication data are divided on
the basis of HLRSN. Every virtual HLR has its own service data (including
subscriber data, global data, template data and authentication data). Therefore,
every virtual HLR can provide service independently.
The HLR can provide differentiated services for every area according to the actual
circumstance of every area. A physical HLR can configure data based on HLRSN
to realize multiple independent virtual HLRs.
Benefits:



The service enables the carrier to deploy a physical HLR for multiple areas for
saving investment. Meanwhile, the operation of an area can operate the virtual
HLR conveniently as if the virtual HLR is a real HLR. The system operability is
very high.

None.
NEs.
WHFD-570500
Function name:
Authority-Based and Domain-Based Management
Specifications:
None.
Overview:
The authority/domain based management is intended to satisfy the requirements
in the management of virtual HLRs. The operators are divided into multiple levels,
and the operators of every level have their own operation rights and number
segment. Different operator has different allocated virtual HLR.
The operators of virtual HLRs are divided into 3 levels:

Operators of level 1 can manage all subscriber data of the HLR.

Operators of level 2 can manage all subscriber data of a virtual HLR.

Operators of level 3 can manage all subscriber data of a portion of a number
segment in a virtual HLR.
The attributes of an operator include:

Name and password of the operator

Virtual HLRSN

Allocated subscriber segment (note: The level-1 operator has no such
attribute; the number segment of a level-2 operator is that of the
corresponding virtual HLR; the number segment of a level-3 operator is the
subset of the number segment of the corresponding virtual HLR)

MML commands
Provided that the subscribers of an HLR are distributed over a province. The
level-1 operator handles the province-level services; the level-2 operator can
handle county/city-level service; the level-3 operator can handle services under
the city/county level.
The HLR has defined an overall IMSI/MSISDN number segment. The number
segment for an operator must fall within the number segment.
Benefits:

The service can improve the operability and network operations security.


None.
NEs.

Huawei HLR9820 Function

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Huawei HLR9820 Function

Hochgeladen von

Copyright:

Verfügbare Formate

Function description of HLR9820 V900R003C04

Huawei HLR9820 Function Description

Das könnte Ihnen auch gefallen