Huawei SingleSDB V100R006C00 HSS9860 Feature Description(HLR and EPC-HSS FE Part)

Huawei SinlgeSDB V100R006C00

HSS9860 Feature Description

(HLR and EPC-HSS FE part)

Issue V 1.0

Date 2014-01-22

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks

and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the commercial contract made between

Huawei and the customer. All or partial products, services and features described in this document may not

be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all

statements, information, and recommendations in this document are provided "AS IS" without warranties,

guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

Huawei SinlgeSDB V100R006C00 HSS9860 Feature Description(HLR and EPC-HSS FE part)

Issue V 1.0 (2014-01-22) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

Page 3 of 191

Contents

1 Basic Features ............................................................................................................................ 5

1.1 Common Features of the 2G/3G/LTE............................................................................... 5

1.1.1 WHFD-403000 O&M Functions ...................................................................................... 5

1.1.2 WHFD-404000 Message Tracing Management ............................................................. 13

1.1.3 WHFD-405000 Reliability Functions ............................................................................ 16

1.1.4 WHFD-405300 HLR Integrate with HSS ...................................................................... 28

1.2 Features of the 2G/3G .................................................................................................... 28

1.2.1 WHFD-200100 Teleservices .......................................................................................... 28

1.2.2 WHFD-200200 Supplementary Services ....................................................................... 32

1.2.3 WHFD-200300 ODB Services ....................................................................................... 47

1.2.4 WHFD-200400 Other Functions .................................................................................... 59

1.2.5 WHFD-200500 Mobility Management .......................................................................... 63

1.2.6 WHFD-200600 Call Processing Functions .................................................................... 73

1.2.7 WHFD-200700 Supplementary Service Management ................................................... 76

1.2.8 WHFD-200800 Protocols and Interfaces ....................................................................... 81

1.3 Features of the LTE ........................................................................................................ 83

1.3.1 WHFD-401000 LTE Mobility Management .................................................................. 83

1.3.2 WHFD-402000 Protocols and Interfaces ....................................................................... 90

2 Optional Features ................................................................................................................... 95

2.1 Common Features of the 2G/3G/LTE............................................................................. 95

2.1.1 WHFD-410100 Service-Specific Functions ................................................................... 95

2.1.2 WHFD-219000 Authentication Center Function(AUC) ................................................. 96

2.1.3 WHFD-210210 Seamless Geographic Redundancy Solution of the HSS9860 ............ 104

2.1.4 WHFD-210220 N+1 Compatibility Redundancy Solution .......................................... 106

2.1.5 WHFD-210230 Automatic FE Switchover ................................................................... 107

2.2 Features of the 2G/3G .................................................................................................. 107

2.2.1 WHFD-211000 CS Data Services ................................................................................ 107

2.2.2 WHFD-212000 GPRS Services ................................................................................... 109

2.2.3 WHFD-213000 Supplementary Services ..................................................................... 112

2.2.4 WHFD-214000 CAMEL Services ................................................................................ 118

2.2.5 WHFD-215000 Other Services and Functions ............................................................. 122

2.2.6 WHFD-216000 Mobility Services ............................................................................... 127




Page 4 of 191

2.2.7 WHFD-217000 Networking Functions ........................................................................ 129

2.2.8 WHFD-218000 Enhanced Functions ........................................................................... 135

2.2.9 WHFD-219000 Authentication Center Function(AUC) ............................................... 168

2.2.10 WHFD-220000 Machine to Machine communications(M2M) .................................... 170

2.3 Features of the LTE ...................................................................................................... 172

2.3.1 WHFD-410102 Wildcard APN..................................................................................... 172

2.3.2 WHFD-410103 IMSI Replacing .................................................................................. 172

2.3.3 WHFD-410104 Inter-working with HLR ..................................................................... 173

2.3.4 WHFD-410200 Roaming-Specific Functions .............................................................. 175

2.3.5 WHFD-410106 Auto-Provisioning for LTE ................................................................. 184

2.3.6 WHFD-410300 Supporting of VoLTE .......................................................................... 186

2.3.7 WHFD-410400 EPS domain-based Global Tracing Function ....... Error! Bookmark not

defined.

2.3.8 WHFD-410500 Authentication Center ............................ Error! Bookmark not defined.

2.3.9 WHFD-410600 SCTP Multi-Homing ............................. Error! Bookmark not defined.




Page 5 of 191

1 Basic Features

1.1 Common Features of the 2G/3G/LTE

1.1.1 WHFD-403000 O&M Functions

For the convenience of operation and maintenance, the SAE-HSS provides the following

operation and maintenance functions:

Security Management

Performance Management

Fault Management

Configuration Management

Equipment Management

1.1.1.1 WHFD-403010 Security Management

Availability

This function has been available since SAE-HSS9820 V900R006.

Specification

N/A

Summary

The security management function allows you to assign operation rights to an operator or a

workstation to protect the system against unauthorized access or operations.

The SAE-HSS allows you to assign operation rights based on command groups. A command

group is comprised of a set of commands according to certain rules. The SAE-HSS supports

32 command groups. Command groups ranging from 10 to 31 are user-defined; the other

command groups are default groups and cannot be modified. You can assign operation rights

to an operator or a workstation by configuring command groups.

The SAE-HSS provides level-based management for operators and workstations. Different

operators and workstations are assigned different operation rights. This mechanism can

prevent unauthorized operations and improve system security.

In addition, the SAE-HSS provides O&M logs for recording the operations and maintenance

conducted by an operator. When problems occur, these logs can help to identify them.

Benefits




Page 6 of 191

For carriers

This function enables carriers to control access to the system by workstations and operators,

making routine operation and maintenance safer and more flexible.

For subscribers

N/A

Description

Linux security enhancement

Linux security is enhanced in terms of services, password configuration, and file

permissions. Therefore, the system is protected against viruses and service processing is

not adversely affected.

System authority control

Rights

Rights are defined as operations that an operator or workstation. They are assigned to an

operator or a workstation based on command groups.

Operator

An operator is the person who manages or operates the system. The operators are graded

according to the levels shown in the following table.

Level Rights

Administrator Querying data, maintaining the system,

configuring data, and managing users

Operator Querying data, maintaining the system, and

configuring data

User Querying data and maintaining the system

Guest Querying data

Custom Assigned by administrator-level operators

Command group

A command group is comprised of a set of commands according to certain rules.

There are 32 command groups in total in the system. The following table describes them

all:

Category Operation Right Modification Allowed

G_ADMIN G_ADMIN contains all the

commands of the system. Only the

user Admin and administrator-level

operators are assigned rights to

G_ADMIN.

The group name

cannot be changed.

Commands cannot be

added to or deleted

from the command

group.




Page 7 of 191

Category Operation Right Modification Allowed

G_OPERA

TOR

Only administrator-level and

operator-level operators are assigned

the rights to G_OPERATOR.

The group name

cannot be changed.

Commands cannot be

added to or deleted

from the command

group.

G_USER Only administrator-level,

operator-level, and user-level

operators are assigned the rights to

G_USER.

The group name

cannot be changed.

Commands cannot be

added to or deleted

from the command

group.

G_GUEST All operators are authorized rights to

G_GUEST. The guest-level operators

are assigned rights to G_GUEST.

The group name

cannot be changed.

Commands cannot be

added to or deleted

from the command

group.

G_0 to

G_9

Only Admin, administrator-level

operators, and NMS operators are

assigned rights to command groups

G_0 to G_9. Custom-level operators

are assigned rights to a part of or all

these command groups.

The group names

cannot be changed.

Commands cannot be

added to or deleted

from these command

groups.

G_10 to

G_31

Only Admin, administrator-level

operators, and NMS operators are

assigned rights to command groups

G_10 to G_31. Custom-level

operators are assigned rights to a part

or all of these command groups.

The group names can

be changed.

Commands can be

added to or deleted

from these command

groups.

The following figure shows the relationship between different command groups.

G_OPERATOR

G_USER

G_GUEST

G_ADMIN




Page 8 of 191

Workstation

A workstation is a computer terminal that is installed with the OMU client and connected

to the OMU server. The SAE-HSS identifies different workstations by IP addresses.

Workstations rights, assigned based on command groups, are graded according to the

four levels shown in the following table.

Level Rights

G_Admin Querying data, maintaining the system,

configuring data, and managing users

G_Operator Querying data, maintaining the system, and

configuring data

G_User Querying data and maintaining the system

G_Guest Querying data

Rights of an operator on a workstation

The rights of an operator on a workstation are the intersection of the rights assigned to

the operator and the rights assigned to the workstation the operator is using. For example,

if an operator has the rights to command groups G_1 and G_2 and the workstation being

used has rights to command groups G_0 and G_1, then that operator can only run the

commands in G_1 on that workstation.

Enhancement

None

Dependency

The SAE-HSS implements this function independently. There are no special requirements for

other NEs.

1.1.1.2 WHFD-403020 Performance Management

Availability


Specification

N/A

Summary

Performance management involves various activities of measuring the performance of a

device and its network such as traffic measurement, system resource measurement, signaling

procedure measurement, and fault management. In the SAE-HSS, the performance

measurement involves system resource measurement and signaling procedure measurement.

In addition to the basic measurement entities, the performance measurement system of the

SAE-HSS allows you to define new measurement entities on the basis of the original

measurement entities. Thus, carriers can collect the required data conveniently and evaluate

the QoS of the network flexibly.

Benefits




Page 9 of 191

For carriers

This function helps carriers to learn about the running status of the system and take

measures to optimize the network.

For subscribers

N/A

Description

Table 1-1 lists the measurement units provided by the SAE-HSS.

Table 1-1 Measurement units provided by the SAE-HSS

Measurement Type Measurement Unit

CGP Global Measurement CPU Rate Measurement

IP Flow Measurement

Memory Occupancy Rate Measurement

Network Interface State Measurement

Service Measurement ULR and ULA Statistics

AIR and AIA Statistics

CLR and CLA Statistics

IDR and IDA Statistics

DSR and DSA Statistics

PUR and PUA Statistics

NOR and NOA Statistics

RSR and RSA Statistics

MAR and MAA Statistics

SAR and SAA Statistics

RTR and RTA Statistics

PPR and PPA Statistics

Diameter Protocol Message Statistics

S6a Message Statistics

SWx Message Statistics

Signaling and Interface

Measurement

SCTP Protocol Internal Message Statistics

SCTP Protocol Global Message Statistics

SCTP Protocol Error Message Statistics

Enhancement




Page 10 of 191

None

Dependency


other NEs.

1.1.1.3 WHFD-403030 Fault Management

Availability


Specification

N/A

Summary

The SAE-HSS provides alarm information output. It reports abnormality that occurs during

the system running. The alarms are output to the alarm maintenance terminal or the alarm

box.

Benefits

For carriers

This function enables carriers to identify the faults in the SAE-HSS and adopt preventive

measures accordingly.

For subscribers

N/A

Description

The alarms generated on the SAE-HSS can be classified into fault alarms and event alarms.

Generally, the fault alarm is more severe than the event alarm. The fault alarm must be

cleared. The event alarm is generated due to an occasional event. It need not be cleared. Some

event alarms recur at a specified time.

The SAE-HSS enables carriers to implement the following alarm management operations:

Query alarm information at any time, and specify alarm severity, alarm type, and/or

generation time to query alarms.

Conveniently learn about each alarm based on explanatory information contained in the

alarm. Then, the carrier can take corresponding measures to clear the alarm.

Enable or disable alarm shielding manually.

The SAE-HSS provides an alarm box. When an alarm is reported, the alarm box generates

siren to alert the maintenance personnel.

Enhancement

None

Dependency




Page 11 of 191


other NEs.

1.1.1.4 WHFD-403040 Configuration Management

Availability


Specification

N/A

Summary

The configuration management function allows you to configure the system, boards, and

interfaces flexibly.

Benefits

For carriers

This function enables carriers to configure the SAE-HSS flexibly and meet various data

configuration requirements.

For subscribers

N/A

Description

The configuration management function allows you to configure data online and offline. It

allows you to configure the data by using MML commands. This simplifies data configuration

because you need to only compile the data configuration scripts.

Enhancement

None

Dependency


other NEs.

1.1.1.5 WHFD-403050 Equipment Management

Availability


Specification

N/A

Summary

The equipment management function allows you to manage the software and hardware of the

equipment conveniently.




Page 12 of 191

Benefits

For carriers

This function enables carriers to manage the SAE-HSS conveniently and meet the

requirements of routine operation.

For subscribers

N/A

Description

Hardware management involves the following:

Resetting a board

Switching over services between boards

Loading data to a board

Other related functions

Software management involves the following:

Loading a patch

Activating a patch

Deactivating a patch

Other related functions

Enhancement

None

Dependency


other NEs.

1.1.1.6 WHFD-403060 Pool-Based Network Management

Availability


Specification

N/A

Summary

This function allows the NMS to manage the SAE-HSS-FE pools on the network in a

centralized way.

Benefits

For carriers

This feature enables carriers to query, manage, and maintain the system information

conveniently.




Page 13 of 191

For subscribers

N/A

Description

The pool-based O&M function is as follows:

The FEs and BEs are present in different pools on the topology view of the NMS.

The O&M MML commands of the same format are issued to all the FEs or BEs in a

pool.

The performance measurement tasks of all the FEs or BEs in a pool are managed in a

centralized way.

Enhancement

None

Dependency

Implementing this function requires the cooperation of Huawei NMS.

1.1.2 WHFD-404000 Message Tracing Management

Signaling tracing management involves interface signaling tracing and subscriber signaling

tracing.

1.1.2.1 WHFD-404010 Interface Signaling Tracing

Availability


Specification

N/A

Summary

The interface signaling tracing function can be used to trace the signaling messages over

various interfaces such as SCTP and Diameter and save the tracing results into files.

Benefits

For carriers

This function enables carriers to trace all messages over an interface. It checks protocol

compliance of messages during the identification of an interconnection fault or interface fault.

For subscribers

N/A

Description

The interface signaling tracing function can be used to trace the following messages:

Signaling Control Transmission Protocol (SCTP) message

Diameter message over the S6a and SWx interfaces




Page 14 of 191

Signaling Connection and Control Part (SCCP) message, Signaling Control

Transmission Protocol (SCTP) message, MTP3-User Adaptation Layer (M3UA)

message, and Message Transfer Part Layer 3 (MTP3) message

MAP/MAP+ signaling messages transmitted over the C, D, Gc, Gr, Lh, and J interfaces

After a tracing task is complete, you can view the file containing the traced messages. The

SAE-HSS provides explanations for the messages in line with standard protocols, allowing

you to understand the message code stream conveniently.

Enhancement

This feature has been enhanced since SAE-HSS9820 V900R006C31：

Signaling Connection and Control Part (SCCP) message, Signaling Control

Transmission Protocol (SCTP) message, MTP3-User Adaptation Layer (M3UA)

message, and Message Transfer Part Layer 3 (MTP3) message

MAP/MAP+ signaling messages transmitted over the C, D, Gc, Gr, Lh, and J interfaces

Dependency


other NEs.

1.1.2.2 WHFD-404020 Subscriber Signaling Tracing

Availability


Specification

N/A

Summary

This function enables you to create a task to trace the signaling messages of a specified

subscriber based on the IMSI or MSIDN over certain interfaces. The system provides online

explanations for the traced messages and saves them in a file.

Benefits

For carriers

This function helps carriers to identify the problems that interrupt the services of a subscriber.

For subscribers

N/A

Description

You can trace the signaling messages of a subscriber over the F or S6a/S6d /SWx 和 C/D，Gc，

Gr，Lh，J interface.

After a tracing task is complete, you can view the file containing the traced messages. The

SAE-HSS provides explanations for the messages in line with standard protocols, allowing

you to understand the message code stream conveniently.




Page 15 of 191

Enhancement


Trace the signaling messages of a subscriber over the F or S6a/S6d /SWx, C/D, Gc, Gr，Lh, J interface.

Dependency


other NEs.

1.1.2.3 WHFD-404030 Equipment Information Management

Availability


Specification

N/A

Summary

This function enables the hardware and software information of the SAE-HSS to be queried

through the OMU or NMS.

Benefits

For carriers

This function enables carriers to query, manage, and maintain the hardware and software

information of the SAE-HSS.

For subscribers

N/A

Description

Equipment information management enables the following information to be queried through

the NMS:

Basic information about the hardware equipment

Connection information, module information, and configuration information

Information about the peer equipment

Version information of the host

Information about the cabinet, subrack, and board, and the Flash E-label of the board

On receiving the command sent from the NMS for generating an equipment archive file, the

OMU server generates an .xml file. The OMU server uploads the generated file to the

specified directory on the NMS based on the command received.

Enhancement


This function enables the hardware and software information of the logic HLR to be

queried through the OMU or NMS, not only SAE-HSS.




Page 16 of 191

Dependency

Implementing this function requires the cooperation of Huawei NMS.

1.1.2.4 WHFD-404050 Pool-Based Network Management

Availability

This function has been available since HLR9820 V900R006.

Specification

None.

Summary

This function allows the NMS to manage the HSS9860-FE pools on the network in a

centralized way.

Benefits

For carriers

This feature enables carriers to query, manage, and maintain the system information

conveniently.

For subscribers

None.

Description

The pool-based O&M function is as follows:

The FEs and BEs are present in different pools on the topology view of the NMS.

The O&M MML commands of the same format are issued to all the FEs or BEs in a

pool.

The performance measurement tasks of all the FEs or BEs in a pool are managed in a

centralized way.

Dependency

The implementation of this function requires the cooperation of Huawei NMS.

1.1.3 WHFD-405000 Reliability Functions

Comprehensive protection measures are adopted in the hardware and software design of the

SAE-HSS to ensure high reliability.

The hardware reliability design of the SAE-HSS includes:

Redundancy and Backup Design (WHFD-405101)

Power Supply Reliability (WHFD-405102)

Distributed Structure of Boards (WHFD-405103)

Distributed Power Supply (WHFD-405104)




Page 17 of 191

IP-Based Dual-Plane Communication (WHFD-405105)

Automatic Adjustment of Fan Speed (WHFD-405106)

The software reliability design of the SAE-HSS includes:

Automatic Fault Detection and Self-Healing (WHFD-405201)

Automatic or Manual Switchover (WHFD-405202)

Overload Control (Flow Control) (WHFD-405203)

System Rollback upon Upgrade Failure (WHFD-405204)

Distributed Structure of Software Modules (WHFD-405205)

Automatic Load Balancing (WHFD-405206)

1.1.3.1 WHFD-405101 Redundancy and Backup Design

Availability

This feature has been available since SAE-HSS9820 V900R006.

Specification

N/A

Summary

The SAE-HSS adopts redundancy and backup design. It achieves redundancy for all the

components.

Benefits

For carriers

This feature enables carriers to enhance system reliability and ensure uninterrupted service

provisioning.

For subscribers

N/A

Description

The faults in some components may lower the bearer capability of the system. To avoid such

adverse impact and enhance system reliability, the SAE-HSS adopts redundancy and backup

design. All the components of the same type work in load-sharing mode. If a component fails,

the other components automatically take over the services of the faulty component, thus

ensuring that the service provisioning of the SAE-HSS is not interrupted.

Enhancement

None

Dependency

The SAE-HSS provides this feature independently. There are no special requirements for

other NEs.




Page 18 of 191

1.1.3.2 WHFD-405102 Power Supply Reliability

Availability


Specification

N/A

Summary

Faults in the power supply may result in a critical disaster. Thus, the SAE-HSS adopts

high-reliability design for the power supply system.

Benefits

For carriers


provisioning.

For subscribers

N/A

Description

The SAE-HSS adopts the following technologies to ensure 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 outside of the allowable range.

Protects the system against voltage drop and lightning.

Provides power-off protection for programs and data.

Protects the system against over-voltage, over-current, and reverse polarity connection.

Enhancement

None

Dependency


other NEs.

1.1.3.3 WHFD-405103 Distributed Structure of Boards

Availability


Specification

N/A

Summary




Page 19 of 191

The distributed structure allows multiple functional entities that are identical in a system to

work in load-sharing mode to implement a certain function. The most distinguished feature of

the distributed structure is resource sharing in the system. When a functional entity fails, the

other functional entities automatically take over the load of the faulty entity, thus ensuring

uninterrupted service provisioning.

The SAE-HSS adopts the distributed design for the boards.

Benefits

For carriers


provisioning.

For subscribers

N/A

Description

The boards of the SAE-HSS adopt the distributed structure and work in load-sharing mode.

When a board is faulty, the other board automatically takes over the services of the faulty

board, thus ensuring uninterrupted service processing.

The switchover of the boards has the following advantages:

When a board fails, the other board immediately takes over the services of the faulty

board.

The switchover is automatically implemented.

The switchover is completed within three seconds.

The services are not interrupted during the switchover.

After the switchover, the system automatically and evenly distributes the load among the

working boards.

Enhancement

None

Dependency


other NEs.

1.1.3.4 WHFD-405104 Distributed Power Supply

Availability


Specification

N/A

Summary


work in load-sharing mode to implement a certain function. The most distinguished feature of

the distributed structure is resource sharing in the system. When a functional entity fails, the




Page 20 of 191

other functional entities automatically take over the load of the faulty entity, thus ensuring

uninterrupted service provisioning.

The SAE-HSS adopts the distributed design for the power supply system.

Benefits

For carriers


provisioning.

For subscribers

N/A

Description

The power modules of the SAE-HSS adopt the distributed structure. When a power module is

faulty, the load is automatically distributed to the other power module, thus ensuring

uninterrupted power supply.

The components of a subrack are divided into two zones: S1 and S2. Two power modules

supply power to the two zones. Module 1 controls a power input (A1) of S1 and a power input

(B1) of S2; Module 2 controls a power input (A2) of S1 and a power input (B2) of S2, as

shown in the following figure.

Enhancement

None

Dependency


other NEs.

1.1.3.5 WHFD-405105 IP-Based Dual-plane Communication

Availability


Specification




Page 21 of 191

N/A

Summary

The SAE-HSS adopts dual planes for IP communications and dual dual-star architecture to

prevent single-point faults. The service plane and the management plane are independent of

each other, thus ensuring system reliability.

Benefits

For carriers


provisioning.

For subscribers

N/A

Description

The SAE-HSS is configured with two SWUs. Each SWU is connected to the service

processing boards in star mode. With the help of the dual-star structure, the service processing

of the system will not be adversely affected by single-point faults.

The service data and management signaling are independently exchanged over two planes.

The two planes are independent of each other, as shown in the following figure, thus ensuring

the reliability of the system.

Enhancement

None

Dependency


other NEs.




Page 22 of 191

1.1.3.6 WHFD-405106 Automatic Adjustment of Fan Speed

Availability


Specification

N/A

Summary

The fan speed can be automatically adjusted based on the temperature of the SAE-HSS.

Benefits

For carriers

This feature lowers the power consumption, thus helping carriers to reduce the operation

cost.

For subscribers

N/A

Description

The SAE-HSS generates heat during the running. The fans dissipate the heat from the subrack,

thus ensuring a proper temperature of the SAE-HSS. The fans of higher speed can achieve

better heat dissipation, but also consume more power. The SAE-HSS can automatically adjust

the speed of fans based on the temperature of the system, thus creating a suitable environment

for the system running and effectively reducing power consumption.

Enhancement

None

Dependency


other NEs.

1.1.3.7 WHFD-405201 Automatic Fault Detection and Self-Healing

Availability


Specification

N/A

Summary

The SAE-HSS adopts real-time fault detection and self-healing designs to ensure the

reliability of its software.

Benefits

For carriers




Page 23 of 191


provisioning.

For subscribers

N/A

Description

The SAE-HSS provides the following functions to implement real-time fault detection and

self-healing:

Detecting hardware/software faults automatically

Staring the fault-handling program automatically to rectify the hardware/software faults

on key components

Performing a switchover if a fault cannot be rectified. The system automatically switches

over services to the standby component, thus ensuring uninterrupted service processing.

Enhancement

None

Dependency


other NEs.

1.1.3.8 WHFD-405202 Automatic or Manual Switchover

Availability


Specification

N/A

Summary

For the components working in active/standby mode, services can be automatically or

manually switched over to the standby component when the active one is faulty.

Benefits

For carriers

This feature enables carriers to enhance system reliability and ensure uninterrupted

service provisioning.

For subscribers

N/A

Description

In the SAE-HSS, the key processing boards that lead in signaling work in active/standby

mode. When the active board is faulty, services are automatically switched over to the standby

board. Manual switchover is generally performed in special cases (such as system upgrade).

Enhancement




Page 24 of 191

None

Dependency


other NEs.

1.1.3.9 WHFD-405203 Overload Control (Flow Control)

Availability


Specification

N/A

Summary

The flow control function prevents congestion when the traffic volume exceeds the upper

threshold of the processing capability of the SAE-HSS.

Benefits

For carriers

This function enables carriers to enhance system reliability, avoid service interruption

resulting from surging traffics, and prevent the avalanche effect.

For subscribers

N/A

Description

The SAE-HSS provides flow control. When congestion occurs due to excessive messages, the

SAE-HSS discards certain messages to ensure normal service processing.

The SAE-HSS adopts the flow control mechanism, which enables the system to run properly

and provide optimal responding to messages even when the traffic is heavy.

Flow control is adopted on the SCCP layer of the service layer to implement smooth

traffic volume adjustment.

When flow control starts, the Diameter messages are processed based on priorities.

The load of processors and resource utilization are monitored and analyzed in real time

to implement adaptive flow control.

The system provides high-speed processing of the commands sent from the provisioning

system. When the traffic exceeds the maximum processing capability of the system, flow

control is adopted to ensure system security.

Flow control parameters can be set to implement forced flow control.

Independent flow control is adopted for subscriber data management and Diameter

operations. The Diameter operations take precedence over subscriber data management.

Enhancement

None

Dependency




Page 25 of 191


other NEs.

1.1.3.10 WHFD-405204 System Rollback upon Upgrade Failure

Availability


Specification

N/A

Summary

The rollback function allows the system to be rolled back when the system upgrade fails. This

function minimizes adverse effect of upgrade failures.

Benefits

For carriers

This function enables carriers to roll back the system upon upgrade failure, thus

minimizing the adverse effect of upgrade failure.

For subscribers

N/A

Description

The SAE-HSS provides the rollback function, which allows the subscriber data and system

version to be restored to previous state when the system upgrade fails. This function

minimizes the adverse effect of upgrade failures.

Enhancement

None

Dependency


other NEs.

1.1.3.11 WHFD-405205 Distributed Structure of Software Modules

Availability


Specification

N/A

Summary


work in load-sharing mode to accomplish a function. The most distinguished feature of the

distributed structure is resource sharing in the system. When a functional entity is faulty, the




Page 26 of 191

load is automatically switched over to other functional entities. Thus, the service provisioning

of the entire system is not adversely affected.

The software modules of the SAE-HSS adopt distributed structure.

Benefits

For carriers

This feature improves system reliability, ensures uninterrupted service processing, and

helps to improve customer satisfaction.

For subscribers

N/A

Description

The SAE-HSS adopts distributed structure. It consists of the following functional layers:

Signaling processing layer

Service processing layer

Data routing layer

Data storage layer

Each layer adopts distributed structure, as shown in Figure 1-2.

Figure 1-2 Distributed structure of functional modules

The signaling processing layer consists of the HSS signaling function (HSF). The HSF and

HSS control function (HCF) constitute the FE. The FE processes signaling and service logics.

The data service layer consists of the DRU and DSU.

HSF

HCF

DRU

HSF …

...

...

HCF

DRU

HSF cluster

HCF cluster

DRU cluster

Signaling

processing

Service

processing

Data

routing

Data

storage

Extended storage

(optional)

DSU cluster

Disk array

DSU cluster DSU cluster …

FE

BE




Page 27 of 191

The data storage layer adopts high reliable commercialized database management system. It

also uses the disk array to provide permanent storage of subscriber data. The hard disks of the

disk array are configured with RAID and hot spare disks to ensure the security of subscriber

data.

The data service layer, subscriber data management layer, and data storage layer constitute the

BE. The BE stores and manages subscriber data, and also provides data service for the Front

End (FE).

The distributed software architecture protects the system against single-point faults and

improves system reliability.

Enhancement

None

Dependency


other NEs.

1.1.3.12 WHFD-405206 Automatic Load Balancing

Availability


Specification

N/A

Summary

The SAE-HSS automatically balances the load among different software modules.

Benefits

For carriers

This feature enables carriers to protect the system from being overloaded and thus prevent

system breakdown.

For subscribers

N/A

Description

During the running of the SAE-HSS, the load may be unbalanced among boards due to the

diversity of tasks, complexity of signaling processing, and number of processed messages.

The SAE-HSS adopts software technology to implement automatic load balancing among

modules of the same type. This improves system stability and reliability.

Enhancement

None

Dependency




Page 28 of 191


other NEs.

1.1.4 WHFD-405300 HLR Integrate with HSS

Availability

This function has been available since SAE-HSS9820 V900R006C31.

Specification

N/A

Summary

This function embeds HLR function into HSS, enable HSS provide both HLR and EPC-HSS

function.

Benefits

For carriers

This function simplifies the network architecture and reduces the OPEX and CAPEX. Provide

more effective interactivity between 2G/3G and LTE.

For subscribers

N/A

Description

HLR and EPC-HSS are deployed in a combined form.

1. HLR and EPC-HSS share the hardware, and improve the hardware usage more

efficiently.

2. The existing HLR (V900R006) can be upgraded to Integrated HSS smoothly.

1.2 Features of the 2G/3G

1.2.1 WHFD-200100 Teleservices

The HLR supports standard teleservices, which include voice services (WHFD-200110) and

short message services (WHFD-200120).

The voice services include the following services:

Telephony service, that is, TS11 (WHFD-200111)

Emergency call, that is TS12 (WHFD-200112)

The length of information sent in a short message is short. Specified by ETSI GSM 03.40 and

ETSI GSM 03.41 in ETSI GSM, a point to point (PTP) short message (SM) can have a

maximum of 140 bytes, that is, 160 ASCII characters or 70 Chinese characters. A broadcast

SM can have 82 bytes per page, that is, 92 ASCII characters or 41 Chinese characters. A

macro broadcast message can have a maximum of 15 pages that are sent consecutively.




Page 29 of 191

The broadcast SMS allows subscribers to receive public information periodically and

selectively. The PTP SMS allows subscribers to send or receive SMs at any time. The

point-to-point SMSs can be classified into the following types:

Short Message MT/PP, that is, TS21 (WHFD-200121)

Short Message MO/PP, that is, TS22 (WHFD-200122)

1.2.1.1 WHFD-200111 Telephony Service (TS11)

Availability

This service has been available since HLR9820 V600.

Specification

3GPP29002

3GPP22003

Summary

This service allows subscribers in the PLMN, PSTN, and ISDN to communicate with each

other through telephones.

Benefits

For carriers

This service allows carriers to provide services to mobile subscribers, thus increasing the

revenue.

For subscribers

Subscriber can enjoy basic voice service.

Description

This service can be provided to or withdrawn from subscribers on the HLR. When this service

is provided to a subscriber or when a subscriber initiates a location update, the HLR delivers

the service subscription data to the VLR. When this service is withdrawn from a subscriber,

the HLR sends a message to the VLR, instructing the VLR to delete the subscriber data.

Enhancement

None

Dependency

The HLR implements this service in compliance with standard protocols.

1.2.1.2 WHFD-200112 Emergency Call (TS12)

Availability


Specification

3GPP29002

3GPP22003

Summary




Page 30 of 191

The service allows subscribers to make calls for requesting emergency assistance (for

example, 112 and 119) without being registered with the network.

Benefits

For carriers

Carriers can provide emergency call service to subscribers.

For subscribers

Subscribers can request emergency assistance as required.

Description

This service is provided to subscribers by default when subscribers are defined in the HLR.

During the location update procedure, the HLR delivers the service subscription data to the

VLR.

Enhancement

None

Dependency


1.2.1.3 WHFD-200121 Short Message MT/PP (TS21)

Availability


Specification

3GPP29002

3GPP23039

3GPP23040

3GPP23041

3GPP24011

3GPP24012

Summary

The short message MT/PP service allows mobile subscribers to receive short messages.

Benefits

For carriers

This service helps to increase the average revenue per user (ARPU).

For subscribers

This service enriches the means of communication. It allows subscribers to communicate

with each other through short messages instead of speech.

Description

The HLR supports the short message MT/PP service. When a short message is sent to a

subscriber who is being called, the short message center (SMC) sends a Sending Rout




Page 31 of 191

Information (SRI) message to the HLR. On receiving an SRI message, the HLR returns a

message based on the subscription information and status of the subscriber.

Feature Enhancement

To increase the success rate in short message reception, the HLR9820 allows the short

message delivery path to be specified for the subscribers who can access the network in both

the CS and PS domain (that is, the subscribers whose network access mode (NAM) is MSC

or SGSN. If NAM is SGSN, the HLR sends the SMC an SRI response carrying the SGSN

address. If NAM is MSC, the HLR sends the SMC an SRI response carrying the MSC

address.

Dependency

The HLR implements this service in compliance with standard protocols. The implementation

of this service requires the cooperation of the SMC.

1.2.1.4 WHFD-200122 Short Message MO/PP (TS22)

Availability


Specification

3GPP29002

3GPP23039

3GPP23040

3GPP23041

3GPP24011

3GPP24012

Summary

The short message MO/PP service allows mobile subscribers to send short messages.

Benefits

For carriers

This service helps to increase the average revenue per user (ARPU).

For subscribers

This service enriches the means of communication. It allows subscribers to communicate

with each other through short messages instead of speech.

Description

The HLR supports the short message MO/PP service. In the location update procedure, the

HLR delivers the service subscription data to the VLR. When a subscriber sends a short

message, the VLR proceeds according to the service subscription information of the

subscriber.

Enhancement

None

Dependency




Page 32 of 191


of this service requires the cooperation of the SMC.

1.2.2 WHFD-200200 Supplementary Services

The HLR9820 provides standard supplementary services, including:

Call forwarding services (WHFD-200210)

Call barring services (WHFD-200220)

Number presentation services (WHFD-200230)

The HLR9820 also provides optional supplementary services, which include Call Waiting

(CW), Call Hold (CH), Multi-Party (MPTY), Unstructured Supplementary Service Data

(USSD), Closed User Group (CUG), and PLMN Specific Supplementary Services

(PLMNSS).

The HLR9820 provides the following call forwarding services:

CFU (WHFD-200211)

CFB (WHFD-200212)

CFNRy (WHFD-200213)

CFNRc (WHFD-200214)

The call barring services can be classified into barring of incoming calls and barring of

outgoing calls. The HLR9820 provides the following call barring services:

BAOC (WHFD-200221)

BOIC (WHFD-200222)

BOIC-exHC (WHFD-200223)

BAIC (WHFD-200224)

BIC-Roam (WHFD-200225)

The HLR9820 provides the following number presentation services:

CLIP (WHFD-200231)

CLIR (WHFD-200232)

COLP (WHFD-200233)

COLR (WHFD-200234)

OVER-CLIR (WHFD-200235)

OVER-COLR WHFD-200236)

1.2.2.1 WHFD-200211 Call Forwarding–Unconditional (CFU)

Availability


Specification

3GPP29002

3GPP22082

3GPP23082

3GPP24082




Page 33 of 191

Summary

The Call Forwarding–Unconditional (CFU) service allows the incoming calls addressed to a

subscriber to be forwarded to another number or a voice mailbox. The forwarded-to number

(FTN) can be the number of a PLMN subscriber, PSTN subscriber, or ISDN subscriber.

Benefits

For carriers

This service helps to increase the call completion rate, which in turn increases the

revenue.

For subscribers

Incoming calls can be forwarded to another number when the called MS/UE is not

available. This service provides more choices for subscribers.

Description

This service can be provided, withdrawn, activated, or deactivated for subscribers on the

HLR.

The HLR stores the FTN and returns the FTN in an SRI response message to the GMSC.

Subscribers can activate the service by using MSs/UEs or in the Customer Service Center.

Enhancement

None

Dependency


1.2.2.2 WHFD-200212 Call Forwarding–Busy (CFB)

Availability


Specification

3GPP29002

3GPP22082

3GPP23082

3GPP24082

Summary

The Call Forwarding–Busy (CFB) service allows the incoming calls addressed to a subscriber

to be forwarded to another number or a voice mailbox when the subscriber is engaged in a

call or service. The FTN can be the number of a PLMN subscriber, PSTN subscriber, or ISDN

subscriber.

The CFB service can be further classified into network-determined CFB and user-determined

CFB.

Benefits




Page 34 of 191

For carriers


revenue.

For subscribers



Description


HLR.

The HLR stores the FTNs. In the location update procedure of a subscriber, the HLR delivers

the FTN to the VLR. When a call is originated to the subscriber and the subscriber is engaged

in another call or service, the VLR sends an SRI message to the HLR serving the

forwarded-to party based on the FTN.


Enhancement

None

Dependency


1.2.2.3 WHFD-200213 Call Forwarding on No Reply (CFNRy)

Availability


Specification

3GPP29002

3GPP22082

3GPP23082

3GPP24082

Summary

The Call Forwarding on No Reply (CFNRy) service allows the incoming calls addressed to a

subscriber to be forwarded to another number or a voice mailbox when the subscriber fails to

answer or is inaccessible. The FTN can be the number of a PLMN subscriber, PSTN

subscriber, or ISDN subscriber.

Benefits

For carriers


revenue.

For subscribers






Page 35 of 191

Description


HLR.

The HLR stores the FTNs. In the location update procedure of a subscriber, the HLR delivers

the FTN and the no-reply time to the VLR. When a call is originated to the subscriber, the

MSC serving the subscriber sends an SRI message to the HLR serving the forwarded-to party

based on the FTN if the subscriber does not answer the call within the specified time.


Enhancement

Huawei HSS9860 allows you to set the no reply time of the CFNRy service.

Usually, the no reply time is set to the default time (30s) for the subscriber. When a subscriber

does not answer a call within the specified time, the system triggers the CFNRy service. The

HLR provides an MML command for modifying the default time. The no reply time can be 5s,

10s, 15s, 20s, 25s, or 30s.

Dependency


1.2.2.4 WHFD-200214 Call Forwarding on mobile subscriber Not Reachable

(CFNRc)

Availability


Specification

3GPP29002

3GPP22082

3GPP23082

3GPP24082

Summary

The Call Forwarding on mobile subscriber Not Reachable (CFNRc) service allows the

incoming calls addressed to a subscriber to be forwarded to another number or a voice

mailbox when the subscriber is unreachable. The FTN can be the number of a PLMN

subscriber, PSTN subscriber, or ISDN subscriber.

Benefits

For carriers


revenue.

For subscribers

Incoming calls can be forwarded to another number when the called MS/UE is switched

off or is not in the service area. This service provides more choices for subscribers.

Description




Page 36 of 191

This service can be provided, withdrawn, activated, or deactivated for subscribers on the HLR.

This service can be activated only after it is provided. Subscribers can activate this service by

using MSs/UEs or in the Customer Service Center.

The CFNRc is implemented in any of the following cases:

A subscriber is reported as inactive for a long time, and the HLR sets the flag, indicating

that the subscriber is not reachable.

In this case, the HLR knows the status of the subscriber. When receiving an SRI message

from the originating MSC, the HLR returns the FTN in an SRI response message. Then,

the originating MSC sends an SRI message to the HLR serving the forwarded-to party

based on the received FTN.

A subscriber switches off its MS/UE or the MS/UE does not respond to paging

In this case, the HLR does not know the subscriber status. When receiving an SRI

message from the originating MSC, the HLR does not return the FTN. The originating

MSC delivers the call to the MSC serving the callee. Then, the MSC serving the callee

sends an SRI message to the HLR serving the forwarded-to party.

Enhancement

None

Dependency


1.2.2.5 WHFD-200215 FTN Analysis and Normalization

Availability

This function has been available since HLR9820 V600.

Specification

None.

Summary

This function allows the FTN of the correct format to be generated when a call forwarding

service is registered.

Benefits

For carriers

This function allows carriers to configure call forwarding policies flexibly.

For subscribers

This function allows subscribers to set the FTNs flexibly.

Description

The request for registering a call forwarding service received by the HLR contains the FTN.

The FTN can be in any of the following formats:

Unknown format (or domestic format): 81 + FTN dialed by the subscriber:

− 81 + PSTN subscriber number

− 81 + 0 + area code + PSTN subscriber number




Page 37 of 191

− 81 + PLMN subscriber number

International format

− 91 + country code (CC)+ area code (AC)+ PSTN subscriber number

− 91 + PLMN subscriber number

At present, the FTNs registered through MSs/UEs are in unknown format. The FTNs stored in

the HLR and the FTNS delivered to the VLR are in international format. Therefore, the HLR

must normalize the received FTNs. The HLR can determine the attributes of the FTNs only

after the FTNs in unknown format are converted into the FTNs in international format.

The FTN analysis and normalized is implemented based on the data configured on the HLR.

Feature Enhancement

The following data must be configured on the HLR:

Local office information

This data table has only one record, which contains the country code of the HLR and the

HLR number. When a country code is required for an FTN, the HLR adds the country

code contained in this table to the FTN.

Mapping between the IMSIs and the area codes

This data table has multiple records. It records the mapping between the prefixes of

IMSIs and the area codes. For example, the IMSI prefix 46000755 maps area code 755.

When an area code is required for an FTN, the HLR adds the area code corresponding to

the IMSI prefix to the FTN.

Called number analysis data

The data table has multiple records. Each record has four fields: prefix of the FTN,

attribute of the FTN, information station flag, and entertainment station flag.

There are four options for the FTN attribute: local number, domestic toll call number,

international toll call number, and PLMN number. For example, 139 indicates a PLMN

number; 0 indicates a domestic toll call number; 00 indicates an international toll call

number; 1 to 9 indicate local numbers.

In the FTN normalization process, the HLR searches for a record in the

CALLEDNUM_ANALYSIS table based on the prefix of an FTN according to the

maximum matching principle.

Area code data

This data table has multiple records. Each record contains the name and cord of an area.

For example, the area code of Shenzhen is 755.

Mapping between the MSISDNs and the area codes

This data table has multiple records. It records the mapping between the prefixes of

MSISDNs and the area codes. When analyzing a PLMN FTN, the HLR queries the table

to check whether the FTN exceeds area limitation imposed on the call forwarding.

Country code data

This data table has multiple records. Each record contains the name and code of a

country. For example, the country code of China is 86. When analyzing an FTN of

international format, the HLR queries the table to check whether the FTN is a domestic

number.

Forbidden FTNs




Page 38 of 191

This data table has multiple records. It records the numbers to which calls cannot be

forwarded, for example, 110. When determining that an FTN is a local number, the HLR

queries this table to verify whether calls can be forwarded to this FTN.

Dependency

The HLR9820 implements this function independently. There is no special requirement for

other NEs.

1.2.2.6 WHFD-200221 Barring of All Outgoing Calls (BAOC)

Availability


Specification

3GPP29002

3GPP22088

3GPP23088

3GPP24088

Summary

The Barring of All Outgoing Calls (BAOC) service prevents a subscriber from originating all

the calls except emergency calls.

Benefits

For carriers

Carriers can provide more value-added services to increase the subscriber base and

revenue.

For subscribers

Subscribers can control call flexibly.

Description

The HLR stores the code and status of the BAOC service and delivers this information to the

VLR. The MSC implements the barring of outgoing calls of a subscriber.


Subscribers can query and modify the service status by using MSs/UEs. Whether the BAOC

service is controlled a subscribers or carrier can be set on the HLR. If the BAOC service is

controlled by a subscriber, the subscriber can activate or deactivate this service by using the

MS/UE. Before activating or deactivating this service on the MS/UE, the subscriber must be

provided with the BAOC service and enter the password. The password can be changed either

on the MS/UE or HLR.

Enhancement

None

Dependency





Page 39 of 191

1.2.2.7 WHFD-200222 Barring of Outgoing International Calls (BOIC)

Availability


Specification

3GPP29002

3GPP22088

3GPP23088

3GPP24088

Summary

The Barring of Outgoing International Calls (BOIC) service prevents the subscribers roaming

in the home PLMN from originating international calls.

Benefits

For carriers


revenue.

For subscribers


Description

The HLR stores the code and status of the BOIC service and delivers this information to the

MSC serving the subscriber. The MSC implements the barring of outgoing international calls

of the subscriber.


Subscribers can query and modify the service status by using MSs/UEs.

Whether the BOIC service is controlled a subscribers or carrier can be set on the HLR. If the

BOIC service is controlled by a subscriber, the subscriber can activate or deactivate this

service by using the MS/UE. Before activating or deactivating this service on the MS/UE, the

subscriber must be provided with the BOIC service and enter the password. The password can

be changed either on the MS/UE or HLR.

Enhancement

None

Dependency


1.2.2.8 WHFD-200223 Barring of Outgoing International Calls Except Those

Directed to the Home PLMN Country (BOIC-exHC)

Availability


Specification




Page 40 of 191

3GPP29002

3GPP22088

3GPP23088

3GPP24088

Summary

The Barring of Outgoing International Calls Except Those Directed to the Home PLMN

Country (BOIC-exHC) service prevents a subscriber from originating international calls

except the calls to the home PLMN.

Benefits

For carriers


revenue.

For subscribers


Description

The HLR stores the code and status of the BOIC-exHC service and delivers this information

to the MSC serving the subscriber. The MSC implements the barring of outgoing international

calls of the subscriber. The BOIC-exHC service is implemented based on the basic service

groups, which include teleservices and bearer services.



Whether the BOIC-exHC service is controlled a subscribers or carrier can be set on the HLR.

If the BOIC-exHC service is controlled by a subscriber, the subscriber can activate or

deactivate this service by using the MS/UE. Before activating or deactivating this service on

the MS/UE, the subscriber must be provided with the BOIC-exHC service and enter the

password. The password can be changed either on the MS/UE or HLR.

Enhancement

None

Dependency


1.2.2.9 WHFD-200224 Barring of All Incoming Calls (BAIC)

Availability


Specification

3GPP29002

3GPP22088

3GPP23088

3GPP24088




Page 41 of 191

Summary

The Barring of All Incoming Calls (BAIC) prevents a subscriber from receiving calls.

Benefits

For carriers


revenue.

For subscribers


Description

The BAIC service can be activated through different basic service groups.

The HLR stores the code of BAIC, information about the basic service groups, and status of

the BAIC service. On receiving an SRI message, the HLR checks whether the subscriber

activates the BAIC service. If the BAIC service is activated, the HLR returns the GMSC a

message, which indicates the all the incoming calls to the subscriber are barred.



Whether the BAIC service is controlled a subscribers or carrier can be set on the HLR. If the

BAIC service is controlled by a subscriber, the subscriber can activate or deactivate this

service by using the MS/UE. Before activating or deactivating this service on the MS/UE, the

subscriber must be provided with the BAIC service and enter the password. The password can

be changed either on the MS/UE or HLR.

Enhancement

None

Dependency


1.2.2.10 WHFD-200225 Barring of Incoming Calls when Roaming Outside the Home

PLMN Country (BIC-ROAM)

Availability


Specification

3GPP29002

3GPP22088

3GPP23088

3GPP24088

Summary

The Barring of Incoming Calls when Roaming Outside the Home PLMN Country

(BIC-ROAM) service prevents the subscriber who is roaming outside the home PLMN

country from receiving calls.




Page 42 of 191

Benefits

For carriers


revenue.

For subscribers

The service helps to boost the MS/UE lease business.

Description

The BIC-ROAM service can be activated through different basic service groups.

The HLR stores the code and status of BIC-ROAM and the information about the basic

service groups. On receiving an SRI message, the HLR checks whether the subscriber

activates the BIC-ROAM service. If the BIC-ROAM service is activated, the HLR returns the

GMSC a message, which indicates the all the incoming calls to the subscriber are barred.



Whether the BIC-ROAM service is controlled a subscribers or carrier can be set on the HLR.

If the BIC-ROAM service is controlled by a subscriber, the subscriber can activate or

deactivate this service by using the MS/UE. Before activating or deactivating this service on

the MS/UE, the subscriber must be provided with the BIC-ROAM service and enter the

password. The password can be changed either on the MS/UE or HLR.

Enhancement

None

Dependency


1.2.2.11 WHFD-200231 Calling Line Identification Presentation (CLIP)

Availability


Specification

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Calling Line Identification Presentation (CLIP) service allows the calling number to be

presented to the callee.

Benefits

For carriers


revenue.




Page 43 of 191

For subscribers

This service allows a subscriber to know the calling number and determine whether to

answer the incoming call. This service is useful in the following scenarios:

− The callee is busy and does not want to answer incoming calls

− The callee wants to reject the calls from specified callers

− The callee wants to call back later

− The callee wants to distinguish business calls from personal calls

Description

The HLR stores the CLIP subscription data. The HLR delivers the CLIP subscription data to

the VLR in the location update procedure or if the CLIP subscription data is modified.

Assume that subscribe B subscribes to the CLIP service. When A calls B, the number of A is

presented to B.

Enhancement

The enhanced CLIP service is implemented based on service groups; that is, the HLR allows

a subscriber to determine whether to display his or her number in a voice call or video call.

The setting of the enhanced CLIP service can be different for voice calls and video calls.

Dependency


1.2.2.12 WHFD-200232 Calling Line Identification Restriction (CLIR)

Availability


Specification

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Calling Line Identification Restriction (CLIR) service prevents the subscriber number

from being displayed to the callee.

Benefits

For carriers


revenue.

For subscribers

This service helps to protect the privacy of subscribers.

Description




Page 44 of 191

The HLR stores the CLIR subscription data. When this service is provided to a subscriber,

one of the following modes can be specified:

Permanent restriction: The CLIR service is activated for all outgoing calls, that is, the

number of the subscriber is not presented to the callee in all outgoing calls.

Temporary permission: The CLIR service is activated only when the mobile subscriber

dials #31#called number.

Temporary restriction: The CLIR service is activated automatically unless the mobile

subscriber dials #31#called number.

If a CLIR service subscriber performs a location update or if the CLIR subscription data is

modified, the HLR delivers the CLIR subscription data to the VLR. When the subscriber

originates a call, the network determines whether to display the calling number to the callee

based on the restriction mode.

Assume that subscriber A subscribes to the CLIR service with the restriction mode set to

permanent restriction and subscriber B subscribes to the CLIP service. When A calls B, the

number of A is not presented to B.

Enhancement

None

Dependency


1.2.2.13 WHFD-200233 Connected Line Identification Presentation (COLP)

Availability


Specification

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Connected Line Identification Presentation (COLP) service allows the FTN to be

presented to the caller when the call addressed to the callee is forwarded.

Benefits

For carriers


revenue.

For subscribers

This service helps to caller to learn about the number to be connected.

Description




Page 45 of 191

The HLR stores the COLP subscription data. If a COLP service subscriber performs a

location update or if the CLOR subscription data is modified, the HLR delivers the CLOR

subscription data to the VLR.

Assume that subscriber A subscribes to the COLP service and subscriber B subscribes to a call

forwarding service with the forwarded-to party of C. When A originates a call to B, the

number of C is presented to A.

Enhancement

None

Dependency


1.2.2.14 WHFD-200234 Connected Line Identification Restriction (COLR)

Availability


Specification

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Connected Line Identification Restriction (COLR) service prevents the number of a

subscriber, who serving as the forwarded-to party, from being presented to the caller.

Benefits

For carriers


revenue.

For subscribers

This service helps to protect the privacy of subscribers.

Description

The HLR stores the COLR subscription data. If a COLR service subscriber performs a

location update or if the COLR subscription data is modified, the HLR delivers the CLOR

subscription data to the VLR.

Assume that subscriber C subscribes to the COLR service and subscriber B subscribes to a

call forwarding service with the forwarded-to party of C. When the call addressed to B is

forwarded to C, the number of C is not presented to the caller.

Enhancement

None

Dependency




Page 46 of 191


1.2.2.15 WHFD-200235 Override Calling Line Identification Restriction

(OVER-CLIR)

Availability


Specification

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Override Calling Line Identification Restriction (OVER-CLIR) service allows the calling

number to be presented to the callee even if the callee has the CLIR active.

Benefits

For carriers


revenue.

For subscribers

This service is applicable to the subscribers who require the information about the caller

before answering calls. It helps to identify the callers who initiate calls for malicious

purposes.

Description

The OVER-CLIR service is an attribute of the CLIP service. When subscribing to the CLIP

service, the subscriber can determine whether to have OVER-CLIR active.

The CLIP service and the CLIR service are mutually exclusive, and CLIR takes precedence

over CLIP. If the caller has CLIR active and the callee has CLIP active, the calling number is

not presented to the callee. The OVER-CLIR service takes precedence over the CLIR service.

If the callee has OVER-CLIR active, the calling number is presented to the callee.

Enhancement

None

Dependency


1.2.2.16 WHFD-200236 Override Connected Line Identification Restriction

(OVER-COLR)

Availability


Specification




Page 47 of 191

3GPP29002

3GPP22081

3GPP23081

3GPP24081

Summary

The Override Connected Line Identification Restriction (OVER-COLR) service allow the

connected number to be present to the caller even if the callee has the COLR active.

Benefits

For carriers


revenue.

For subscribers

This service is applicable to the subscribers who require the information about the callee

to be connected. It can effectively present calls from being forwarded for malicious

purposes.

Description

The OVER-COLR service is an attribute of the COLP service. When subscribing to the COLP

service, the subscriber can determine whether to have OVER-COLR active.

The COLP service and the COL service are mutually exclusive, and COLR takes precedence

over COLP. If the caller has COLP active and the forwarded-to party has COLR active, the

FTN is not presented to the caller. The OVER-COLR service takes precedence over the

COLR service. If the caller has OVER-COLR active, the FTN is presented to the caller.

Enhancement

None

Dependency


1.2.3 WHFD-200300 ODB Services

The Operator-Determined Barring (ODB) services allow carriers to control the incoming and

outgoing calls of subscribers.

The ODB is applicable to all terminal services and bearer services except emergency calls.

The ODB services take precedence over other supplementary service. That is, when an ODB

service conflicts with a supplementary service, the ODB service is implemented.

The difference between the call barring services and the ODB services is as follows:

The status of the ODB services can be controlled only by carriers. The status of call

barring services can be controlled by either carriers or subscribers.

The ODB services are activated automatically upon provisioning. The call barring

services must be activated by either carriers or subscribers.

The ODB services provided by the GU HLR can be classified into the following types:

Call-based ODB (WHFD-200310)




Page 48 of 191

ODB supplementary service management (WHFD-200321)

Roaming-based ODB (WHFD-200330)

The call-based ODB services include the following:

ODB-BAOC (WHFD-200311)

ODB-BOIC (WHFD-200312)

ODB-exHC (WHFD-200313)

ODB-OBCROAM (WHFD-200314)

ODBPB1 (WHFD-200315)

ODB-BAIC (WHFD-200316)

ODB-BICROAM (WHFD-200317)

ODB-Barring of Outgoing Premium Rate Calls (Information) (WHFD-200318)

ODB-Barring of Outgoing Premium Rate Calls (Entertainment) (WHFD-200319)

The GU HLR also provides ODB supplementary service management (WHFD-200321).

The roaming-based ODB services include the following:

ODB-BROHPLMN (WHFD-200331)

ODB-BROHPLMNC (WHFD-200332)

1.2.3.1 WHFD-200311 ODB-Barring of All Outgoing Calls (ODB-BAOC)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of All Outgoing Calls (ODB-BAOC) prevents a subscriber from

originating calls.

Benefits

For carriers

Carriers can flexibly control the services provided for subscribers, especially for the

liable subscribers, thus protecting the interests of carriers.

For subscribers

Subscribers can flexibly select the required services, thus avoiding unnecessary call

charge.

Description

The HLR stores the service subscription data and delivers the subscription information to the

VLR when a service subscriber performs a location update or when the subscription data is

modified. The MSC implements the barring of calls.

Enhancement




Page 49 of 191

None

Dependency


1.2.3.2 WHFD-200312 ODB-Barring of Outgoing International Calls (ODB-BOIC)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Outgoing International Calls (ODB-BOIC) service prevents the

subscribers roaming in the home PLMN from originating international calls.

Benefits

For carriers


liable subscribers, thus protecting the interests of carriers. In addition, carriers can

provide more value-added services to increase the subscriber base and revenue.

For subscribers


charge.

Description




Enhancement

None

Dependency


1.2.3.3 WHFD-200313 ODB-Barring of Outgoing Calls when Roaming Outside the

Home PLMN Country (ODB-exHC)

Availability


Specification

3GPP29002

3GPP22041




Page 50 of 191

Summary

The ODB-Barring of Outgoing Calls when Roaming Outside the Home PLMN Country

(ODB-exHC) service prevents a subscriber from originating international calls except the

calls to the home PLMN.

Benefits

For carriers




For subscribers


charge.

Description




Enhancement

None

Dependency


1.2.3.4 WHFD-200314 ODB-Barring of Outgoing Calls when Roaming Outside the

Home PLMN Country (ODB-BOCROAM)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Outgoing Calls when Roaming Outside the Home PLMN Country

(ODB-BOCROAM) service prevents the subscriber who is roaming outside the home PLMN

country from originating calls.

Benefits

For carriers




For subscribers




Page 51 of 191


charge.

Description




Enhancement

None

Dependency


1.2.3.5 WHFD-200315 ODB-PLMN Baring Type 1 (ODBPB1)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-PLMN Baring Type 1 (ODBPB1) prevents the domestic toll calls.

Benefits

For carriers




For subscribers


charge.

Description

The GU HLR provides four types of customized ODB services, namely, ODBPB1, ODBPB2,

ODBPB3, and ODBPB4. The ODBPB1 service restricts domestic toll calls. The other three

types of services can be customized by carriers. The implementation of this service requires

the cooperation of the MSC.



modified.

Enhancement

None

Dependency




Page 52 of 191


1.2.3.6 WHFD-200316 ODB-Barring of Incoming Calls (ODB-BAIC)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Incoming Calls (ODB-BAIC) service prevents a subscriber from

receiving calls.

Benefits

For carriers




For subscribers


charge.

Description

The HLR stores the service subscription data but does not deliver the subscription data to the

VLR.

On receiving an SRI message from the GMSC, the HLR queries whether the subscriber

subscribes to this service. If yes, the HLR returns the GMSC a message, which indicates that

the incoming calls of the subscriber are restricted.

Enhancement

None

Dependency


1.2.3.7 WHFD-200317 ODB-Barring of Incoming Calls when Roaming Outside the

Home PLMN Country (ODB-BICROAM)

Availability


Specification

3GPP29002

3GPP22041

Summary




Page 53 of 191

The ODB-Barring of Incoming Calls when Roaming Outside the Home PLMN Country

(ODB-BICROAM) prevents the subscriber who is roaming outside the home PLMN country

from receiving calls.

Benefits

For carriers




For subscribers


charge.

Description

The HLR stores the service subscription data but does not deliver the subscription data to the

VLR.

On receiving an SRI message from the GMSC, the HLR queries whether the subscriber

subscribes to this service. If the subscriber subscribes to this service and is roaming outside

the HPLMN country, the HLR returns the GMSC a message, which indicates that the

incoming calls of the subscriber are restricted.

Enhancement

None

Dependency


1.2.3.8 WHFD-200318 ODB-Barring of Outgoing Premium Rate Calls (Information)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Outgoing Premium Rate Calls (Information) service can prevent a

subscriber from originating premium rate calls for information.

Benefits

For carriers




For subscribers




Page 54 of 191


charge.

Description




Enhancement

None

Dependency


1.2.3.9 WHFD-200319 ODB-Barring of Outgoing Premium Rate Calls

(Entertainment)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Outgoing Premium Rate Calls (Entertainment) service prevents a

subscriber from originating premium rate calls for entertainment.

Benefits

For carriers




For subscribers


charge.

Description




Enhancement

None

Dependency





Page 55 of 191

1.2.3.10 WHFD-200321 ODB Supplementary Service Management

Availability


Specification

3GPP29002

3GPP22041

Summary

The GU HLR allows ODB services to be provided or withdrawn for subscribers.

Benefits

For carriers




For subscribers


charge.

Description

The ODB services are activated automatically once they are provided through the HLR. The

HLR delivers the subscription information to the VLR when a service subscriber performs a

location update or when the subscription information is modified. The MSC implements the

barring of calls.

Subscribers cannot perform the operations such as activating, deactivating, registering, or

deregistering the ODB service through MSs/UEs.

Enhancement

None

Dependency

The HLR implements this function independently.

1.2.3.11 WHFD-200331 ODB-Barring of Roaming Outside the Home PLMN

(ODB-BROHPLMN)

Availability


Specification

3GPP29002

3GPP22041

Summary




Page 56 of 191

The ODB-Barring of Roaming Outside the Home PLMN (ODB-BROHPLMN) service

prevents the subscriber who is roaming outside the home PLMN from receiving and

originating calls.

Benefits

For carriers




For subscribers


charge.

Description



modified.

If an ODB-BROHPLMN service subscriber roams outside the home PLMN, the location

update of the subscriber fails.

Enhancement

None

Dependency


1.2.3.12 WHFD-200332 ODB-Barring of Roaming Outside the Home PLMN Country

(ODB-BROHPLMNC)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-Barring of Roaming Outside the Home PLMN Country (ODB-BROHPLMNC)

service prevents the subscriber who is roaming outside the home PLMN country from

receiving and originating calls.

Benefits

For carriers




For subscribers




Page 57 of 191


charge.

Description




If a BROHPLMNC service subscriber roams outside the home PLMN country, the location

update of the subscriber fails.

Enhancement

None

Dependency


1.2.3.13 WHFD-200340 ODB-barring of registration of call forwarded-to number

(ODB-RCF)

Availability


Specification

3GPP29002

3GPP22041

Summary

The ODB-barring of registration of call forwarded-to number (ODB-RCF) service prevents

the FTNs from being registered.

Carriers can prevent any of the following types of FTNs to be registered:

All the FTNs

International FTNs

All international FTNs except those belonging to the HPLMN country

Benefits

For carriers




For subscribers

This service can prevent the call forwarding caused by operations performed by mistake.

Description







Page 58 of 191

For example, if a subscriber subscribes to this service with the registration of all FTNs being

restricted, the subscriber cannot register any FTN on the MS/UE.

Feature Enhancement

The HLR implements this service in compliance with standard protocols. The HLR sends the

subscription data to the related NE, and the MSC implements the barring of calls.

The restrictions on the FTNs can also be set on the HLR. For example, whether calls can be

forwarded to the same area, whether calls can be forwarded to an international number, and

whether the FTNs can contain the country code can be set through data configuration or by

using templates on the HLR.

This service allows carriers to provide different forwarding policies for different subscriber

groups.

Enhancement

None

Dependency


1.2.3.14 WHFD-200350 ODB-Barring of Explicit Call Transfer (ODB-ECT)

Availability


Specification

3GPP22041

3GPP29002

Summary

The ODB-Barring of Explicit Call Transfer (ODB-ECT) service prevents a subscriber from

using the ECT service.

Benefits

For carriers




For subscribers

None.

Description

The HLR stores the subscription data and delivers the subscription data to the VLR when a

service subscriber performs a location update or when the subscription data is modified. The

MSC implements the barring of calls.

The MSC can implement the following types of barring:

Barring all explicit call transfers




Page 59 of 191

Barring explicit call transfer when the served subscriber pays for either or both of the

incoming and outgoing calls

Barring explicit call transfer when the served subscriber roaming abroad pays for either

or both of the incoming and outgoing calls

Barring of explicit call transfer when the served subscriber roaming in another zone pays

for either or both of the incoming and outgoing calls

Barring of explicit call transfer when the served subscriber pays for both of the incoming

and outgoing calls

Barring explicit call transfer when there is an ongoing transferred call for the served

subscriber and at the same time, another subscriber originates a call to this subscriber in

the same MSC/VLR

Enhancement

None

Dependency


1.2.4 WHFD-200400 Other Functions

The GU HLR provides the following services:

Lock of liable subscribers (WHFD-200401)

Subscriber-applied suspension (WHFD-200402)

Subscriber category setting (Subscriber Category) (WHFD-200403)

Multi-NDC (WHFD-200404)

Alternative Processing for Unsupported Services(WHFD-200405)

1.2.4.1 WHFD-200401 Lock of Liable Subscribers

Availability


Specification

None.

Summary

This function allows carriers to suspend services for liable subscribers.

Benefits

For carriers

Carriers can suspend the telephone service, short message service, and GPRS service for

liable subscribers in time to prevent loss of profit.

For subscribers

This function can prevent bill shock, which is caused when subscribers use services

without being aware of the balance.

Description




Page 60 of 191

The GU HLR provides lock management, which allows carriers to suspend services for liable

subscribers and provide services for subscribers who repay the service fees.

The lock management allows carriers to perform one of the following operations:

Restrict or allow the incoming calls of a subscriber

Restrict or allow the outgoing calls of a subscriber

Restrict or allow the GPRS services for a subscriber

Through the above control mechanisms, carriers can restrict the subscriber's services flexibly.

This function facilitates service management.

Feature Enhancement

The GU HLR also provides lock management in the MSC and lock management in the PS

domain. The lock management is performed based on the network access mode (NAM) of

subscribers. If the NAM is MSC and SGSN, the locked subscriber can only access the CS

domain and cannot originate or receive calls or perform USSD operations or GPRS operations.

If the NAM is SGSN, the locked subscriber cannot access the PS domain.

Enhancement

None

Dependency


other NEs.

1.2.4.2 WHFD-200402 Subscriber-Applied Suspension

Availability


Specification

None.

Summary

This function allows carriers to suspend services based on the application of subscribers.

Benefits

For carriers

Carriers can suspend services for subscribers as required.

For subscribers

Subscribers can select required services, thus avoiding unnecessary charges.

Description

The service suspension is implemented through call barring services. When applying for

service suspension or service provisioning, subscribers must go to the Customer Service

Center.




Page 61 of 191

Feature Enhancement

The difference between the service suspension through lock management and the

subscriber-applied suspension is as follows:

Lock management is a carrier-oriented function, whereas subscriber-applied suspension

is a subscriber-oriented function.

Lock management is implemented through ODB services, whereas subscriber-applied

suspension is implemented through call barring supplementary services.

Dependency


other NEs.

1.2.4.3 WHFD-200403 Subscriber Category Setting

Availability


Specification

3GPP29002

3GPP23008

Summary

This function allows carriers to divide subscribers into different categories.

Benefits

For carriers

This function facilitates subscriber management and service management.

For subscribers

None.

Description

Each IMSI is allocated a subscriber category. The GU HLR supports the following subscriber

categories:

UNKNOWN

FRENCH

ENGLISH

GERMAN

RUSSIAN

SPANISH

SPECIAL

RESERVE

COMMON

SUPERIOR

DATACALL




Page 62 of 191

TESTCALL

SPARE

PAYPHONE

COIN

The HLR delivers the information about the subscriber category to the VLR for call

processing or charging.

Enhancement

None

Dependency


1.2.4.4 WHFD-200404 Multi-NDC

Availability


Specification

None.

Summary

The multi-NDC function allows a network to be configured with multiple National

Destination Code (NDCs).

Benefits

For carriers

This function facilitates network planning and data configuration.

For subscribers

None.

Description

The MSISDN consists of the CC, NDC, and SN. The NDC, also called the network number,

identifies the carrier who provides services for a subscriber. An NDC is 1 to 3 digits long.

The GU HLR supports multiple NDCs, that is, it can provide non-differentiated services for

subscribers with different NDCs.

Enhancement

None

Dependency


other NEs.




Page 63 of 191

1.2.4.5 WHFD-200405 Alternative Processing for Unsupported Services

Availability


Specification

None.

Summary

The GU HLR provides alternative functions if the NEs on the network do not support certain

services, such as the ODB, AoCC, and CUG.

Benefits

For carriers

The function helps to improve network compatibility and configurability and service

processing capability. It provides multiple choices for data configuration.

For subscribers

None.

Description

The ISD response message sent from the MSC/VLR to the HLR contains the information

about the services or functions that are not supported by the MSC/VLR. On receiving an ISD

response message, the HLR triggers the alternative procedure according to the data

configuration.

Enhancement

None

Dependency


other NEs.

1.2.5 WHFD-200500 Mobility Management

The GU HLR provides protocol-compliant mobility management, which involves the

following:

Location management (WHFD-200510)

Authentication management (WHFD-200520)

Subscriber management (WHFD-200530)

Fault recovery (WHFD-200540)

The GU HLR provides the following location management functions:

Location update (WHFD-200511)

Location cancellation (WHFD-200512)

Purge MS (WHFD-200513)




Page 64 of 191

Authentication, as an important function in the mobile communication system, can prevent

unauthorized MS from accessing the wireless network. During the authentication process, the

MS and network perform calculations by using the shared parameters (generated by the

network), same algorithm, and keys stored in the MS and network respectively. If the same

results are produced, the MS is allowed to access the network.

The GU HLR provides the following authentication management functions:

Providing the authentication information

Providing the authentication failure report

The GU HLR provides the following subscriber management functions:

Insert subscriber data (WHFD-200531)

Delete subscriber data (WHFD-200532)

The GU HLR provides the following fault recovery functions:

Reset (WHFD-200541)

Restore (WHFD-200542)

Check SS indication (WHFD-200543)

1.2.5.1 WHFD-200511 Location Update

Availability


Specification

3GPP29002

Summary

Location update is initiated by the MS to maintain subscriber data consistency between the

VLR and the HLR.

Benefits

For carriers

None.

For subscribers

None.

Description

The HLR stores the information about the service subscription, location, and status of

subscribers. In the location update procedure of an MS, the HLR delivers the subscription

information of the subscriber to the VLR.

Feature Enhancement

The location update procedure is initiated by the MS. In the GSM system, the HLR, VLR, and

MS (or the SIM card) store the subscriber location information. The location information

stored in the HLR, VLR, and MS must be consistent.




Page 65 of 191

On detecting better signal strength in a location area, the MS sends an access request to the

MSC/VLR (generally, the MSC and VLR are physically integrated) in the target location area.

If the source location area and the target location area are served by the same MSC/VLR, only

the location information of the subscriber in the VLR needs to be updated. If the source

location area and the target location area are not served by the same MSC/VLR, the

MSC/VLR in the target location area sends a message to the HLR to query the information

about the MS. The HLR sends the required information to the MSC/VLR in the target

location area and informs the MSC/VLR in the source location to delete the subscriber

information. After the MS accesses the target location area, the HLR updates the MSC/VLR

number of the subscriber.

The network determines whether the source and target location areas are served by the same

MSC by querying the MS information from the MSC/VLR in the target location area. If the

MSC/VLR in the target location area stores the IMSI of the MS, the source and target location

areas are served by the same MSC. The network can obtain the IMSI of an MS from the

PVLR (the VLR in the source location area) or from the MS.

Location update can be classified into the following types:

Normal location update.

Periodic location update

IMSI attached/detached

A location update request is sent to the HLR in any of the following cases:

An MS initiates a location update procedure.

An MS initiates a service operation as the HLR status is set to Faulty.

Dependency

The HLR implements this function in compliance with standard protocols.

1.2.5.2 WHFD-200512 Location Cancellation

Availability


Specification

3GPP29002

Summary

Location cancellation is initiated by the HLR to delete subscriber data from the VLR.

Benefits

For carriers

None.

For subscribers

None.

Description

To ensure that the subscriber data existing on the network is unique and up-to-date, the HLR

initiates the location cancellation procedure in any of the following cases:




Page 66 of 191

When a subscriber roams from one VLR to another VLR, the HLR sends a location

cancellation message to the previous VLR, requesting the VLR to delete the subscriber

data.

When a subscriber is deleted from the HLR or a new SIM card is provided for a

subscriber, the HLR sends a location cancellation message to the serving VLR,

requesting the VLR to delete the original subscriber data.

Enhancement

None

Dependency


1.2.5.3 WHFD-200513 Purge MS

Availability


Specification

3GPP29002

Summary

If a subscriber is not registered with the network for a long time, the VLR sends a Purge MS

message to the HLR. The HLR then sets the subscriber status to unreachable.

Benefits

For carriers

This function minimizes unnecessary traffic over the network.

For subscribers

None.

Description

When a subscriber is not registered with the network for a certain period (the time can be

controlled by the VLR), the VLR initiates the Purge MS procedure by sending a message to

the HLR. On receiving the message, the HLR sets the Purge flag to a value that indicates that

the subscriber is unreachable currently.

Feature Enhancement

In certain service processing procedures, the HLR is required to provide the status of a

subscriber. The HLR can obtain the subscriber status from the VLR, for example, the HLR

sends a Provide_Subscriber_Info (PSI) message to the VLR. In addition, the VLR can inform

the HLR of the status of a subscriber when the subscriber status changes. The Purge MS

procedure is initiated by the VLR to inform the HLR that an MS is not registered with the

network for a long time. On receiving the message, the HLR records the subscriber status.

When the subscriber status is required in other service processing procedures, the HLR need

not query the subscriber status from the VLR, thus reducing unnecessary traffic over the

network and increasing service processing efficiency.

Dependency




Page 67 of 191


1.2.5.4 WHFD-200521 Provide Authentication Information

Availability


Specification

3GPP29002

Summary

The HLR provides the authentication set on receiving a request from the VLR.

Benefits

For carriers

This function prevents unauthorized MSs/UEs from accessing telecommunication

networks and protects the interests of carriers.

For subscribers

This function can prevent fraudulent use of an MS/UE, thus protecting the interests of

subscribers. In addition, the GU HLR on 3G networks supports the authentication of

networks, thus minimizing the adverse effect of network fraudulence on subscribers.

Description

The HLR9820 supports authentication of 2G and 3G subscribers, and supports authentication

triplet for 2G subscribers and authentication quintuple for 3G subscribers.

The HLR9820 supports the following authentication algorithms:

Authentication algorithms for subscribers using SIM cards: XOR, COMP128_1,

COMP128_2, COMP128_3, and MILENAGE

Authentication algorithm for subscribers using USIM cards: MILENAGE

The HLR9820 adopts active and standby subscriber authentication data reuse counters. Each

authentication set (five authentication triplets) can be reused for a maximum of three times.

If the active counter is not 0, the HLR sends the authentication set corresponding to the active

counter in a message to the VLR and reduces the value of the active counter by 1.

If the active counter is 0 and the standby counter is not 0, the HLR sends the authentication

set corresponding to the standby counter in a message to the VLR and reduces the value of the

standby counter by 1.

If the active and standby counters are 0, the HLR calculates the authentication set by using the

function which is used to calculate the AUC), sets the counters to the maximum value, and

then sends the calculated authentication set in a message to the VLR.

Feature Enhancement

The HLR9820 supports the authentication of both 2G and 3G subscribers. In the

authentication of 2G subscribers, the HLR9820 delivers the authentication triplets (SRES, KC,

and RAND). In the authentication of 3G subscribers, the HLR9820 delivers authentication

quintuplets (MAC, XRES, CK, IK, and AK). In addition, the authentication of 3G subscribers

supports the authentication of the network.




Page 68 of 191

The authentication f a 2G subscriber is implemented as follows:

On receiving a registration request from an MS/UE, the VLR/SGSN sends the HLR/AuC an

authentication request carrying the IMSI of the subscriber.

The HLR/AuC generates the RAND, calculates the authentication vectors (SRES, KC, and

RAND), and sends the authentication vectors to the VLR/SGSN.

The MSC/VLR sends an authentication command (containing the RAND) to the MS/UE. The

MS/UE calculates the SRESms based on the RAND and the KI stored in the MS/UE, and

sends the SRESms in a response message to the MSC/VLR.

If SRESms is equal to SRESauc, the subscriber is allowed to access the network.

Otherwise, the subscriber is not allowed to access the network.

The authentication f a 3G subscriber is implemented as follows:

On receiving a registration request from an MS/UE, the VLR/SGSN sends the HLR/AuC an

authentication request carrying the IMSI of the subscriber.

The HLR/AuC generates the SQN and RAND, calculates the authentication vectors (MAC,

XRES, CK, IK, and AK), and sends the authentication vectors to the VLR/SGSN.

The functions of authentication vectors are as follows:

− The MS/UE uses the MAC to verify the validity of the network.

− The network uses the XRES to verify the validity of the MS/UE.

− The CK and IK are used for data encryption and data integrity verification over the

air interface.

− The AK is used to encrypt the SQN.

The SQN is used to ensure the uniqueness of the authentication vector between the MS

and the VLR/SGSN. Different authentication vectors are used for the authentication, thus

ensuring that the CK and IK used in each call are calculated based on different RANDs.

In addition, the MAC used in each authentication is produced by using the SQN, which

is a variable that is increased by 1. Thus, the key used in each authentication is unique. It

can effectively prevent data security.

The AMF is another parameter used to calculate the authentication vectors. The default

value of the AMF varies according to the equipment vendor. The AMF of Huawei HLR

is set to 0x762C by default.

On receiving the authentication vectors, the VLR/SGSN sends RAND||AUTN to the MS/UE,

requesting the MS/UE to generate authentication data and verify SQN.

On receiving the authentication request, the MS/UE calculates the XMAC, and then compares

the XMAC with the MAC of the AUTN. If the XMAC is different from the MAC, the MS/UE

sends a message to the VLR to reject the authentication request. Meanwhile, the MS/UE

verifies whether the received SQN is within the valid range. If the SQN is invalid, the MS/UE

sends a synchronization failure message to the VLR. If the previous two verifications are

successful, the MS/UE calculates the RES and sends the RES to the VLR/SGSN.

On receiving the RES, the VLR/SGSN compares the RES with the XRES. If the RES is equal

to the XRES, the authentication is successful. Otherwise, the authentication fails.

Dependency





Page 69 of 191

1.2.5.5 WHFD-200522 Authentication Failure Report

Availability


Specification

3GPP29002

Summary

The HLR supports the procedure initiated by the VLR to inform the VLR of the

authentication failure of subscribers.

Benefits

For carriers

This function helps carriers to identify authentication fails and make statistics.

For subscribers

None.

Description

When an authentication fails, the VLR sends the HLR a message carrying the cause of the

authentication failure. The cause of authentication failure can be subscriber response error or

network signature error.

On receiving the message, the HLR returns a response message.

Enhancement

None

Dependency


1.2.5.6 WHFD-200531 Insert Subscriber Data

Availability


Specification

3GPP29002

Summary

When the subscriber data stored in the HLR is modified, the HLR sends the VLR an Insert

Subscriber Data message, instructing the VLR to update the subscriber data.

This function can ensure data consistency between the VLR and the HLR when the data

stored in the HLR is modified.

Benefits




Page 70 of 191

For carriers

This function ensures data consistency between the VLR and the HLR.

For subscribers

None.

Description

The HLR inserts (delivers) subscriber data to the VLR in any of the following procedures:

In the location update procedure, the HLR delivers all the subscription data of a

subscriber to the VLR.

When the subscriber data stored in the HLR is modified, the HLR delivers the updated

subscriber data to the VLR.

When the VLR initiates a data restoration procedure, the HLR delivers the subscriber

data to the VLR to ensure data consistency between the VLR and the HLR.

Feature Enhancement

If the VLR does not support the related service after receiving the Insert Subscriber Data

message from the HLR, the HLR can continue the service processing according to the data

configuration.

For example, if the Insert Subscriber Data message delivered to the VLR carries the data of

the ODB-BAOC service which is not supported by the VLR, the HLR can reject the location

update request of the subscriber or delivers the BAOC service data to the VLR according to

the data configuration.

Dependency


1.2.5.7 WHFD-200532 Delete Subscriber Data

Availability


Specification

3GPP29002

Summary

When the data of a subscriber is deleted from the HLR, the HLR sends the VLR a Delete

Subscriber Data message, instructing the VLR to delete the subscriber data. This function can

ensure data consistency between the HLR and the VLR when the data stored in the HLR is

deleted.

Benefits

For carriers

This function improves the fault recovery capability of the network and ensures data

consistency between the VLR and the HLR.

For subscribers

None.




Page 71 of 191

Description

When a service is withdrawn from a subscriber, the HLR sends a Delete Subscriber Data

message to the VLR, instructing the VLR to delete the subscriber data.

Enhancement

None

Dependency


1.2.5.8 WHFD-200541 Reset

Availability


Specification

3GPP29002

Summary

When the HLR is restored, it sends the VLR a Reset message, instructing the VLR to retrieve

data from the HLR. This function can ensure data consistency between the HLR and the VLR

when a fault occurs on the HLR.

Benefits

For carriers

This function ensures data consistency between the VLR and the HLR.

For subscribers

None.

Description

The GU HLR supports standard reset procedure. To prevent data inconsistency between the

HLR and the VLR when the HLR restarts because of a fault, the HLR sends a Reset message

to the VLR, instructing the VLR to retrieve data from the HLR. On receiving a Reset message,

the VLR updates all the subscriber data associated with the HLR.

The Reset procedure can be initiated automatically or manually. During the migration of the

HLR, the Reset procedure needs to be manually initiated to ensure data consistency between

the HLR and the VLR.

Enhancement

None

Dependency





Page 72 of 191

1.2.5.9 WHFD-200542 Restore

Availability


Specification

3GPP29002

Summary

When the VLR is restored, the VLR sends the HLR a Restore message, requesting the

subscriber data from the HLR. This function can ensure data consistency between the HLR

and the VLR when the VLR is faulty.

Benefits

For carriers

This function improves the fault recovery capability of the network and ensures data

consistency between the VLR and the HLR.

For subscribers

None.

Description

On receiving the Restore message from the VLR, the HLR delivers subscriber data to the

VLR, thus ensuring data consistency between the VLR and HLR.

When the data of a subscriber in the VLR is labeled "untrustworthy" or when the VLR fails to

identify the MSRN based on the Send Roaming Message sent from the HLR, the VLR sends a

Restore message to the HLR. The VLR can send a Restore message to update the data of a

subscriber.

Enhancement

None

Dependency


1.2.5.10 WHFD-200543 Check SS Indication

Availability


Specification

3GPP29002

Summary

When the supplementary service data stored in the HLR9820 is changed, the HLR9820 can

inform the subscriber of the data change.




Page 73 of 191

Benefits

For carriers

This function helps to improve the ARPU.

For subscribers

Subscribers can learn about the service subscription conveniently.

Description

After the HLR restarts, the HLR sends a MAP_FORWARD_CHECK_SS_INDICATION

message to the VLR. The VLR then forwards the message to the MSC. The MSC informs the

subscriber of the service data change.

This procedure is incorporated in the location update procedure as a subscriber initiates a

location update after the HLR restarts. This procedure is bidirectional.

Enhancement

None

Dependency


1.2.6 WHFD-200600 Call Processing Functions

Call processing is the basic service provided by mobile networks. When a call is originated,

the MSC serving the caller is required to obtain the routing information of the called. On the

mobile network, the mobile station roaming number (MSRN) is provided as the routing

information of the callee. Based on the MSRN, the MSC serving the caller directs the call to

the MSC serving the callee for connection.

After a call is originated, the GMSC sends a MAP_SEND_ROUTING_INFORMATION

message to the HLR, requesting the routing information. On receiving the message, the HLR

sends a MAP_PROVIDE_ROAMING_NUMBER message to the MSC/VLR serving the

callee, requesting the MSRN. The MSC/VLR serving the callee sends the MSRN in a

MAP_PROVIDE_ROAMING_NUMBER ACK message to the HLR. The HLR then sends

the MSRN in a MAP_SEND_ROUTING_INFORMATION ACK message to the GMSC.

Figure 1-3 shows the basic call processing procedure.




Page 74 of 191

Figure 1-3 Call processing procedure

GMSC HLR VLR

MAP_SEND_ROUTING_INFORMATION

MAP_PROVIDE_ROAMING_NUMBER

MAP_PROVIDE_ROAMING_NUMBER ACK

MAP_SEND_ROUTING_INFORMATION ACK

The HLR provides the following call processing functions:

Send routing information(WHFD-200601)

Provide roaming number (WHFD-200602)

1.2.6.1 WHFD-200601 Send Routing Information

Availability


Specification

3GPP29002

Summary

On receiving a Send Routing Information (SRI) message from the GMSC, the HLR delivers

the MSRN in a SRI response message to the GMSC.

Benefits

For carriers

None.

For subscribers

None.

Description

The SRI message is initiated by the GMSC. On receiving an SRI message, the HLR checks

the subscription data of the subscriber and then determine whether to obtain the MSRN or

return an error code or an FTN to the GMSC.

If the subscriber has the CFU service active, the HLR returns the FTN in an SRI

response message to the GMSC.




Page 75 of 191

If the callee is a roaming subscriber, the HLR obtains the MSRN from the MSC serving

the callee and sends the MSRN in a SRI response message to the GMSC.

The error code can be unknown subscriber, call barring, forwarding restriction, or absent

subscriber.

Feature Enhancement

The HLR9820 can process calls based on the configured bearer capability

If the received SRI message carries the ISDN-BC (bearer capability), the HLR first converts

ISDN-BC into the GSM-BC, and then translates it into the basic service code. If the

subscriber subscribes to the basic service, the HLR sends a PRN message to the VLR.

If the received SRI message does not carry the ISDN-BC, the HLR initiates a PRN message

according to the default basic service of the subscriber.

The HLR9820 supports multiple MSISDNs. If a call is originated to an auxiliary MSISDN,

the HLR obtains the basic service code based on the auxiliary MSISDN and sends a PRN

message to the VLR.

Dependency


1.2.6.2 WHFD-200602 Provide Roaming Number

Availability


Specification

3GPP29002

Summary

The HLR sends a Provide Roaming Number (PRN) message to the VLR. After obtaining the

MSRN, the HLR sends the MSRN in an SRI response message to the GMSC.

Benefits

For carriers

None.

For subscribers

None.

Description

On receiving an SRI message, the HLR sends a PRN message to the MSC/VLR serving the

callee, requesting the MSRN. The MSC/VLR serving the callee sends the MSRN in a PRN

response message to the HLR. The HLR then sends the MSRN in a SRI response message to

the GMSC.

Enhancement

None

Dependency




Page 76 of 191


1.2.7 WHFD-200700 Supplementary Service Management

The GU HLR provides supplementary service management, which involves the following

operations:

SS registration (WHFD-200701)

SS withdrawal (WHFD-200702)

SS activation (WHFD-200703)

SS deactivation (WHFD-200704)

SS query (WHFD-200705)

SS password registration (WHFD-200706)

SS password verification (WHFD-200707)

1.2.7.1 WHFD-200701 SS Registration

Availability


Specification

3GPP29002

Summary

Subscribers can register supplementary services by using MSs/UEs.

Benefits

For carriers

Carriers can provide subscriber-oriented service procedures.

For subscribers

Subscribers can register supplementary services by using MSs/UEs without going to the

Customer Service Center.

Description

A subscriber can register a call forwarding service by using the MS/UE as long as the call

forwarding service is provided for subscriber on the provisioning system. The service

registration is implemented based on the basic service group. For example, either voice-based

call forwarding service or data-based call forwarding service can be registered.

During the registration, the subscriber enters the FTN on the MS/UE. On receiving a

RegisterSS message, the HLR stores the FTN registered by the subscriber and sets the service

status to Activated. Then, the HLR delivers the call forwarding service data to the VLR.

Enhancement

None

Dependency





Page 77 of 191

1.2.7.2 WHFD-200702 SS Withdrawal

Availability


Specification

3GPP29002

Summary

Subscribers can withdraw supplementary services by using MSs/UEs.

Benefits

For carriers


For subscribers

Subscribers can withdraw supplementary services by using MSs/UEs without going to

the Customer Service Center.

Description

A subscriber can withdraw a call forwarding service by using the MS/UE. The service

withdrawal is implemented based on the basic service group. For example, either voice-based

call forwarding service or data-based call forwarding service can be withdrawn.

On receiving an Erase SS message, the HLR deletes the FTN from the HLR and sets the

service status to Provided but Inactive. Then, the HLR delivers the call forwarding service

data to the VLR.

Enhancement

None

Dependency


1.2.7.3 WHFD-200703 SS Activation

Availability


Specification

3GPP29002

Summary

Subscribers can activate supplementary services by using MSs/UEs.

Benefits

For carriers




Page 78 of 191


For subscribers

Subscribers can activate supplementary services by using MSs/UEs without going to the

Customer Service Center.

Description

A subscriber can activate a call barring service by using the MS/UE as long as the call barring

service is provided for subscriber on the provisioning system. The service activation is

implemented based on the basic service group. For example, either voice-based call barring

service or data-based call barring service can be activated.

On receiving an Activate SS message, the HLR sets the service status to Activated. Then, the

HLR delivers the call barring service data to the VLR.

Enhancement

None

Dependency


1.2.7.4 WHFD-200704 SS Deactivation

Availability


Specification

3GPP29002

Summary

Subscribers can deactivate supplementary services by using MSs/UEs.

Benefits

For carriers


For subscribers

Subscribers can deactivate supplementary services by using MSs/UEs without going to

the Customer Service Center.

Description

A subscriber can deactivate a call barring service by using the MS/UE. The service

deactivation is implemented based on the basic service group. For example, either

voice-based call barring service or data-based call barring service can be deactivated.

On receiving a Deactivate SS message, the HLR sets the service status to Deactivated. Then,

the HLR delivers the call barring service data to the VLR.

Enhancement

None




Page 79 of 191

Dependency


1.2.7.5 WHFD-200705 SS Query

Availability


Specification

3GPP29002

Summary

Subscribers can query the status of supplementary services by using MSs/UEs.

Benefits

For carriers


For subscribers

Subscribers can conveniently learn about the service information.

Description

A subscriber can query the status of the call forwarding service and call barring service by

using the MS/UE. On receiving an Interrogate SS message, the HLR delivers the service

status to the MSC. The query result is displayed on the MS/UE.

Enhancement

None

Dependency


1.2.7.6 WHFD-200706 SS Password Registration

Availability


Specification

3GPP29002

3GPP22004

Summary

Subscribers can change the password, which is used for activating a supplementary service,

by using MSs/UEs.

Benefits

For carriers




Page 80 of 191

Carriers can provide the basic service security verification for subscribers.

For subscribers

This function ensures service operation security.

Description

The initial password is required when a subscriber sets the password for a supplementary

service on the MS/UE. The default password is 0000.

Then, the subscriber is required to enter the new password. The new password must be

entered two times for confirmation. When activating a supplementary service on the MS/UE,

the subscriber is required to enter the password.

Enhancement

None

Dependency


1.2.7.7 WHFD-200707 SS Password Verification

Availability


Specification

3GPP29002

3GPP22004

Summary

When activating a supplementary service using the MS/UE, subscribers are required to enter

the password. If incorrect password is entered, the service activation cannot be performed

successfully.

Benefits

For carriers

Carriers can provide the basic service security verification for subscribers.

For subscribers

This function ensures service operation security.

Description

The password is required before a subscriber activates a supplementary service or modifies

the password of a supplementary service using the MS/UE. The HLR interacts with the MSC

to verify the validity of the subscriber.

Enhancement

None

Dependency




Page 81 of 191


1.2.8 WHFD-200800 Protocols and Interfaces

The GU HLR supports MAP protocols and standard interfaces such as C, D, J, Gc, Gr, and Lh

interfaces.

1.2.8.1 WHFD-200801 Supporting MAP Protocols

Availability

This feature has been available since HLR9820 V600.

Specification

3GPP29002

Summary

The GU HLR supports the following MAP protocols:

MAP Phase 1

MAP Phase 2

Benefits

For carriers

The GU HLR supports diversified services and smooth network evolution.

For subscribers

None.

Description

The GU HLR supports MAP Phase 1 and MAP Phase 2. It supports forward compatibility,

which allows smooth evolution towards later versions.

Enhancement

None

Dependency

The HLR provides this feature in compliance with standard protocols.

1.2.8.2 WHFD-200802 Supporting C, D, J, Gc, Gr, and Lh Interfaces

Availability


Specification

3GPP29002

Summary

The GU HLR supports the following interfaces:




Page 82 of 191

C interface (HLR–MSC interface)

D interface (HLR–VLR interface)

J interface (HLR–gsmSCF) interface)

Gc interface (HLR–GGSN interface)

Gr interface (HLR–SGSN interface)

Lh interface (HLR–GMLC interface)

The GU HLR supports the following bearer modes:

MTP2

MTP3

SCCP

TCAP

MAP

Benefits

For carriers

The GU HLR supports standard interfaces, thus facilitating interconnection between

NEs.

For subscribers

None.

Description

Figure 1-4 shows the interfaces supported by the GU HLR.

Figure 1-4 Interfaces supported by the GU HLR

Enhancement

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

GcGr

GMLC

Lg

Lh

Lg

Lc

J




Page 83 of 191

None

Dependency

The HLR provides this feature in compliance with standard protocols.

1.3 Features of the LTE

1.3.1 WHFD-401000 LTE Mobility Management

The SAE-HSS provides protocol-compliant mobility management, which involves the

following:

Location management (WHFD-401100)

Authentication management (WHFD-401200)

Subscriber management (WHFD-401300)

Fault recovery (WHFD-401400)

The SAE-HSS provides the following location management functions:

Location update (WHFD-401101)

Location cancellation (WHFD-401102)

Purge UE (WHFD-401103)

Authentication, as an important function in the mobile communication system, can prevent

unauthorized UEs from accessing the network. During the authentication process, the UE and

network perform calculations by using the shared parameters (generated by the network),

same algorithm, and keys stored in the UE and network respectively. If the same results are

produced, the UE is allowed to access the network.

The SAE-HSS provides standard authentication management, that is, authentication

information retrieval (WHFD-401201).

The SAE-HSS provides the following subscriber management functions:

Insert subscriber data (WHFD-401301)

Delete subscriber data (WHFD-401302)

The SAE-HSS provides standard fault recovery functions, that is, reset (WHFD-401401).

The SAE-HSS provides the notification request function (WHFD-401500)

1.3.1.1 WHFD-401101 Location Update

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary




Page 84 of 191

The Update Location Request (ULR) is initiated by the UE to maintain subscriber data

consistency between the Mobility Management Entity (MME) and the SAE-HSS.

Benefits

For carriers

N/A

For subscribers

N/A

Description

The SAE-HSS stores the information about the service subscription, location, and status of

subscribers. In the location update procedure of a UE, the SAE-HSS delivers the subscription

information of the subscriber to the MME.

Feature Enhancement

The location update procedure is initiated by the UE. In the LTE or SAE system, the

SAE-HSS, MME, and UE (or the USIM card) store the subscriber location information. The

location information stored in the SAE-HSS, MME, and UE must be consistent.

On detecting better signal strength in a location area, the UE sends an access request to the

MME in the target location area. If the source location area and the target location area are

served by the same MME, only the subscriber location information in the MME needs to be

updated. If the source location area and the target location area are not served by the same

MME, the MME in the target location area sends a message to the SAE-HSS to query the

information about the UE. The SAE-HSS sends the required information to the MME in the

target location area and informs the MME in the source location to delete the subscriber

information. After the UE accesses the target location area, the SAE-HSS updates the MME

number of the subscriber.

The network determines whether the source and target location areas are served by the same

MME by querying the UE information from the MME in the target location area. If the MME

in the target location area stores the IMSI of the UE, the source and target location areas are

served by the same MME. The network can obtain the IMSI of a UE from the previous MME

or from the UE.

Location update can be classified into the following types:

Normal location update.

Periodic location update

IMSI attached/detached

An Update Location Request (ULR) is sent to the SAE-HSS in any of the following cases:

A UE initiates a location update procedure.

A UE initiates a service operation as the HLR status is set to Faulty.

If HSS send a Reset to MME and/or SGSN, The MME or SGSN may include dynamic APN

and PGW ID data in the list of Active-APN AVPs, in order to restore this information in the

HSS after a Reset procedure. the HSS will delete all the stored dynamic PDN GW

information, if there are any, and then replace them by the PDN GW information received in

the list of Active-APN AVPs.

Dependency




Page 85 of 191

The SAE-HSS implements this function in compliance with standard protocols.

1.3.1.2 WHFD-401102 Location Cancellation

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary

Location cancellation is initiated by the SAE-HSS to delete subscriber data from the MME.

Benefits

For carriers

N/A

For subscribers

N/A

Description

To ensure that the subscriber data existing on the network is unique and up-to-date, the SAE

initiates the location cancellation procedure in any of the following cases:

When a subscriber roams from one MME to another MME, the HLR sends a Cancel

Location Request (CLR) to the previous MME, requesting the MME to delete the

subscriber data.

When a subscriber is deleted from the SAE-HSS or a new USIM card is provided for a

subscriber, the HLR sends a CLR to the serving MME, requesting the MME to delete the

original subscriber data.

Enhancement

None

Dependency


1.3.1.3 WHFD-401103 Purge UE

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary




Page 86 of 191

If a subscriber is not registered with the network for a long time, the MME sends a Purge UE

Request (PUR) to the SAE-HSS. The SAE-HSS then sets the subscriber status to unreachable.

Benefits

For carriers

This function minimizes unnecessary traffic over the network.

For subscribers

N/A

Description

When a subscriber is not registered with the network for a certain period (the time can be

controlled by the MME), the MME initiates a Purge UE procedure by sending a PUR to the

SAE-HSSR. On receiving a PUR, the HLR sets the Purge flag to a value that indicates that

the subscriber is unreachable currently.

Feature Enhancement

In certain service processing procedures, the SAE-HSS is required to provide the status of a

subscriber. The SAE-HSS can obtain the subscriber status from the MME, or the MME can

inform the SAE-HSS of the subscriber status. The Purge UE procedure is initiated by the

MME to inform the SAE-HSS that a UE is not registered with the network for a long time. On

receiving a PUR, the SAE-HSS records the subscriber status. When the subscriber status is

required in other service processing procedures, the SAE-HSS need not query the subscriber

status from the MME, thus reducing unnecessary traffic over the network and increasing

service processing efficiency.

Dependency


1.3.1.4 WHFD-401201 Authentication Information Retrieval

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary

The SAE-HSS provides the authentication set on receiving an Authentication Information

Retrieval (AIR) request from the MME.

Benefits

For carriers

This function prevents unauthorized MSs/UEs from accessing telecommunication

networks and protects the interests of carriers.

For subscribers




Page 87 of 191

This function prevents fraudulent use of MS/UE, thus protecting the interests of

subscribers. In addition, the SAE-HSS supports authentication of networks, thus

minimizing the adverse effect of network fraudulence on subscribers.

Description

The SAE-HSS supports 3GPP EPS-AKA authentication, authentication quadruple (RAND,

XRES, AUTH, and KASME) used for authentication of LTE/SAE subscribers, and KDF

algorithm.

Enhancement

None

Dependency


1.3.1.5 WHFD-401301 Insert Subscriber Data

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary

When the subscriber data stored in the SAE-HSS is modified, the HLR sends the MME an

Insert subscriber Data Request (IDR), instructing the MME to update the subscriber data.

This function can ensure data consistency between the MME and the SAE-HSS when the data

stored in the SAE-HSS is modified.

Benefits

For carriers

This function ensures data consistency between the MME and the SAE-HSS.

For subscribers

N/A

Description

The SAE-HSS inserts (delivers) subscriber data to the MME in any of the following

procedures:

In the location update procedure, the SAE-HSS delivers all the subscription data of a

subscriber to the MME.

When the subscriber data stored in the SAE-HSS is modified, the SAE-HSS delivers the

updated subscriber data to the MME.

When the MME initiates a data restoration procedure, the SAE-HSS delivers the

subscriber data to the MME to ensure data consistency between the MME and the

SAE-HSS.

Feature Enhancement




Page 88 of 191

If the MME does not support the related service after receiving an IDR from the SAE-HSS,

the HLR can deliver the data of the alternative service according to the data configuration.

Dependency


1.3.1.6 WHFD-401302 Delete Subscriber Data

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary

When the data of a subscriber is deleted from the SAE-HSS, the SAE-HSS sends the MME a

Delete Subscriber data Request (DSR), instructing the MME to delete the subscriber data.

This function can ensure data consistency between the SAE-HSS and the MME when the data

stored in the SAE-HSS is deleted.

Benefits

For carriers

This function ensures data consistency between the SAE-HSS and the MME when the

data stored in the SAE-HSS is deleted.

For subscribers

N/A

Description

When a service is withdrawn from a subscriber, the SAE-HSS sends a DSR to the MME,

instructing the MME to delete the subscriber data.

Enhancement

None

Dependency


1.3.1.7 WHFD-401401 Fault Recovery

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary




Page 89 of 191

When the SAE-HSS is restored from a failure, it sends the MME a Reset message, instructing

the MME to retrieve data from the SAE-HSS. This function can ensure data consistency

between the SAE-HSS and the MME when a fault occurs on the SAE-HSS.

Benefits

For carriers

This function ensures data consistency between the SAE-HSS and the MME and

improves fault recovery capability of the network.

For subscribers

N/A

Description

The SAE-HSS supports standard reset procedure. To prevent data inconsistency between the

SAE-HSS and the MME when the SAE-HSS restarts because of a fault, the SAE-HSS sends a

Reset message to the MME, instructing the MME to retrieve data from the SAE-HSS. On

receiving a Reset message, the MME updates all the subscriber data associated with the

SAE-HSS.

The Reset procedure can be initiated automatically or manually. During the migration of the

SAE-HSS, the Reset procedure needs to be manually initiated to ensure data consistency

between the SAE-HSS and the MME.

Enhancement

None

Dependency


1.3.1.8 WHFD-401402 Notification Request

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary

The MME sends the SAE-HSS a Notification Request (NOR) in any of the following cases:

The UE information is updated without performing a location update

The PDN-GW allocated by an APN for a UE is reallocated, updated, or deleted.

Benefits

For carriers

This function ensures data consistency between the SAE-HSS and the MME and

improves fault recovery capability of the network.

For subscribers

N/A




Page 90 of 191

Description

The MME sends the SAE-HSS a Notification Request (NOR) in any of the following cases:

The UE information is updated without performing a location update

The PDN-GW allocated by an APN for a UE is reallocated, updated, or deleted.

Enhancement

None

Dependency


1.3.2 WHFD-402000 Protocols and Interfaces

The SAE-HSS supports the Diameter protocol and interfaces (including the S6a and SWx

interfaces) and the interface to the provisioning system.

1.3.2.1 WHFD-402010 Supporting the Diameter Protocol

Availability


Specification

RFC 3588

Summary

The SAE-HSS supports the Diameter protocol.

Benefits

For carriers

This feature helps carriers to provide more services and realize network evolution.

For subscribers

N/A

Description

The SAE-HSS supports the Diameter protocol on the service layer.

Enhancement

None

Dependency

The SAE-HSS provides this feature in compliance with standard protocols.

1.3.2.2 WHFD-402020 Supporting the S6a/S6d Interface

Availability




Page 91 of 191


Specification

3GPP TS 23401

3GPP TS 29272

Summary

The SAE-HSS interacts with the MME through the S6a interface.

The SAE-HSS supports IP, SCTP, and Diameter.

Benefits

For carriers

N/A

For subscribers

N/A

Description

The SAE-HSS interacts with the MME through the S6a interface.

Enhancement


Support interacts with the S4-SGSN through the S6d interface.

Dependency


1.3.2.3 WHFD-402030 Supporting the SWx Interface (Non-3GPP)

Availability


Specification

3GPP TS 23401

3GPP TS 29272

Summary




Page 92 of 191

The SAE-HSS interacts with the AAA through the SWx interface.


Benefits

For carriers

N/A

For subscribers

N/A

Description

The SAE-HSS interacts with the AAA through the SWx interface.

Enhancement

None

Dependency


1.3.2.4 WHFD-402040 Supporting connect DRA(Diemeter Router Agent)

Availability

This feature has been available since SAE-HSS9820 V900R006C31.

Specification

RFC 3588

3GPP TS 29272

Summary

When HSS send a Diameter message, it relay the message to DRA(Diameter Routing Agent).

The DRA will routes and forwards the message to destination.




Page 93 of 191

Benefits

For carriers

Simplify and reduce the network connections.

For subscribers

N/A

Description

HSS can create multiple links with DRA and the links are work in load share mode. when one

link failed, other links will take over it.

HSS can connect with multiple DRAs, when one DRA failed, the HSS will send the Diameter

message to others. The selection of DRAs can be load share mode or primary-secondary

mode.

Enhancement

None

Dependency


1.3.2.5 WHFD-402060 Supporting the SLh Interface

Availability


Specification

3GPP TS 23271

3GPP TS 29173

Summary

The SAE-HSS interacts with the GMLC through the SLh interface.


Benefits

For carriers

N/A

For subscribers

N/A

Description

The function of SLh interface is same as Lh interface. However, Lh is map based protocol and

SLh is diameter based protocol.




Page 94 of 191

Enhancement

None

Dependency





Page 95 of 191

2 Optional Features

2.1 Common Features of the 2G/3G/LTE

2.1.1 WHFD-410100 Service-Specific Functions

2.1.1.1 WHFD-410101 Access Restriction Data (ARD)

Availability

This service has been available since SAE-HSS9820 V900R006C03.

Specification

3GPP29002, 3GPP 23401, 3GPP 23402, 3GPP 29272, 3GPP 29273.

Summary

The Access Restriction Data (ARD) service allows carriers to control the GSM subscribers'

access to the UMTS network.

Benefits

For carriers

This service allows carriers to control 2G subscribers' access to the UMTS network, and

reasonably arrange and open the network resources for the subscribers.

For subscribers

This service allows subscribers to access the radio network according to the actual

requirement.

Description

The HLR is added with the access restriction flag. The access restriction flag is transmitted

between the HLR and the VLR or SGSN through the extended MAP Inserted Subscriber Data

(ISD). After receiving the ISD, the VLR or SGSN determines whether to allow the subscriber

access based on the access restriction flag carried in the ISD and the radio access system that

serves the subscriber. If the subscriber access is denied, the VLR or SGSN returns a message

carrying the cause value. The cause value can be flexibly configured by carriers. Assume that

a subscriber has subscribed to the ARD service whose data is

GREANAllowed/UTRANNOTAllowed and that the local MSOFTX3000 supports ARD 3G

restriction. When the subscriber attempts to access the local network from the 3G UTRAN,

the location update fails because of access restriction. Consequently, 2G subscriber's access to

the 3G network is under control.




Page 96 of 191

The SAE-HSS supports multiple types of access, such as GERAN, UTRAN, E-UTRAN, and

non-3GPP IP. Access restriction allows the SAE-HSS to control the access of UEs, thus

facilitating the network operation and maintenance.

Enhancement

None

Dependency


of this service requires the cooperation of the MSC and VLR.

2.1.2 WHFD-219000 Authentication Center Function(AUC)

The authentication function is defined according to a protocol and is implemented by the

Authentication Center (AuC). Incorporating the AuC function, the HLR supports 3GPP

standard authentication procedures and the relevant authentication encryption algorithms.

The HLR supports the KI encryption (WHFD-219200) function. To ensure the security, the KI

data is encrypted during its transfer from the card manufacturer to the carrier. The HLR

supports the loading of the encrypted KI data and stores the encrypted KI data in the database.

Meanwhile, the key is also encrypted to ensure the security of the KI data.

The HLR uses K4 as the key, and encrypts and decrypts KI data by using the DES or AES

algorithm. The subscriber can select different K4s for encrypting the KI.

2.1.2.1 WHFD-219201 DES Algorithm

Availability


Specification

None.

Summary

The Data Encryption Standard (DES) is a symmetric-key algorithm invented by IBM in 70s

of last century. Currently, it has been widely used in every field.

Benefits

For carriers

The DES algorithm provides high security. Without the key, it is difficult to decrypt the

KI data. Therefore, the DES algorithm can effectively protect the KI data and ensure the

security of the subscriber's authentication data.

For subscribers

None.

Description

The key of the DES algorithm is 56 bits long (or 64 bits long if the parity check bits are

considered). The DES is a block cipher encryption algorithm that takes 64 bits as a block.




Page 97 of 191

The HLR uses K4 as the key, and encrypts and decrypts KI data by using the DES algorithm.

Enhancement

None

Dependency

The HLR implements this feature independently. There is no special requirement for other

NEs.

2.1.2.2 WHFD-219202 AES Algorithm

Availability

This feature has been available since HLR9820 V900R003.

Specification

None.

Summary

The Advanced Encryption Standard (AES) is the next generation encryption standard. It is the

most advanced encryption technology in the world and features fast speed and high security.

Benefits

For carriers

The AES algorithm provides high security. It can effectively protect the KI data and

ensure the security of the subscriber's authentication data.

For subscribers

None.

Description

The AES is a cryptographic algorithm announced by the National Institute of Standards and

Technology (NIST) on November 15th, 2002, as a replacement for the DES. The AES series

consist of various algorithms and testing standards of modules, including the Advanced

Encryption Standard (AES) in Federal Information Processing Standards Publication (FIPS

PUB) 197 and the Advanced Encryption Standard Algorithm Validation Suite (AESAVS)

designed by the NIST.

Enhancement

None

Dependency


NEs.

2.1.2.3 WHFD-410530 COMP128-1 Algorithm

Availability





Page 98 of 191

Specification

3GPP29002

Summary

The HLR supports the COMP128-1 algorithm.

Benefits

For carriers

This feature provides basic authentication algorithm to meet network authentication

requirements.

For subscribers

None.

Description

The COMP128-1 is a standard algorithm that realizes the A3 algorithm and the A8 algorithm.

The A3 algorithm is also referred to as the authentication algorithm. It calculates the SRES

based on the RAND generated by the HLR/AuC and the authentication key KI of the SIM

card. The SRES is used to identify a mobile subscriber.

The A8 algorithm is also referred to as the encryption key generator. It calculates the

encryption key Kc based on the RAND and KI. The A5 algorithm uses Kc as the key to

encrypt the signaling data and subscriber data transmitted over encrypted channels.

Enhancement

None

Dependency

The HLR implements this feature in compliance with standard protocols. The implementation

of this feature requires the cooperation of the MSC and VLR.


Availability


Specification

3GPP29002

Summary


Benefits

For carriers

The COMP128-1 is widely used in the GSM network. Therefore, the security of the

GSM network is not well protected. In comparison, the COMP128-2 algorithm is more

competitive and can protect the authentication security better.




Page 99 of 191

For subscribers

None.

Description








Enhancement

None

Dependency




Availability


Specification

3GPP29002

Summary


Benefits

For carriers

Compared with the COMP128-2, the COMP128-3 algorithm can protect the

authentication security better.

For subscribers

None.

Description











Page 100 of 191

Enhancement

None

Dependency



2.1.2.6 WHFD-410560 Milenage Algorithm

Availability


Specification

3GPP29002

3GPP35205

3GPP35206

Summary

The HLR supports the 3G Milenage authentication algorithm.

Benefits

For carriers

This feature can satisfy the requirements of 3G UE and network for authentication

algorithms.

For subscribers

None.

Description

The Milenage authentication algorithm is an authentication algorithm adopted in the 3G

network. The USIM card supports the Milenage authentication algorithm only.

Enhancement

None

Dependency



2.1.2.7 WHFD-219700 G-Milenage Algorithm

Availability


Specification

3GPP29002

3GPP35205




Page 101 of 191

3GPP35206

Summary

The HLR supports the G-Milenage authentication algorithm. The G-Milenage algorithm is the

Milenage algorithm adopted in the GSM network.

Benefits

For carriers

This feature can satisfy the requirements of 2G MS and network for authentication

algorithms. It supports multiple authentication algorithms.

For subscribers

None.

Description

The G-Milenage authentication algorithm is an authentication algorithm adopted in the GSM

network. The SIM card supports the G-Milenage authentication algorithm. The G-Milenage

algorithm differs from the Milenage algorithm in the calculation result. To be specific, the

result calculated by using the Milenage algorithm is a quintuple, and the result calculated by

using the G-Milenage algorithm is a triplet; that is, the G-Milenage algorithm converts the

quintuple into triplet.

Enhancement

None

Dependency



2.1.2.8 WHFD-219800 XOR Algorithm

Availability


Specification

None.

Summary

The HLR supports the XOR authentication algorithm.

Benefits

For carriers

This feature can satisfy the requirements of 2G MS and network for authentication

algorithms. It supports multiple authentication algorithms.

For subscribers

None.

Description




Page 102 of 191

The XOR authentication algorithm is an authentication algorithm adopted in the GSM

network. The XOR algorithm calculates the SRES and Kc 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 A5 algorithm uses Kc as the key to encrypt the signaling data and

subscriber data transmitted over encrypted channels.

Enhancement

None

Dependency

The implementation of the XOR algorithm requires the cooperation of the MSC/VLR and

MSC.

2.1.2.9 WHFD-219900 CAVE38 Algorithm

Availability


Specification

None.

Summary

The HLR supports the CAVE38 authentication algorithm (CAVE38: the private authentication

algorithm used in MOTO iDEN system, and it is used for GSM authentication).

Benefits

For carriers

This feature can satisfy the requirements of iDEN system MS and network for

authentication algorithms. It supports multiple authentication algorithms.

For subscribers

None.

Description

MOTOROLA company iDEN system is integrated Digital Enhanced Network, it is used for

Centrex network of company. iDEN system adopts CAVE38 private authentication algorithm,

and the parameter of algorithm is the same as the GSM authentication parameters, but the KI

is 64 bit.

Enhancement

None

Dependency

The implementation of the CAVE38 algorithm requires the cooperation of the MSC/VLR and

MSC.




Page 103 of 191

2.1.2.10 WHFD-410510 Support of SIM-AKA Authentication

Availability


Specification

N/A

Summary

This function enables the SAE-HSS to calculate the triplet used for SIM-AKA authentication

and send it to the MME when a SIM-card subscriber attempts to access the LTE/SAE

network.

Benefits

For carriers

This function enables carriers to provide the LTE/SAE services to 2G subscribers. This

helps to enhance carriers' competitive edge.

For subscribers

This function enables 2G subscribers to subscribe to the LTE/SAE services without

changing SIM cards.

Description

The SAE-HSS supports the SIM-AKA authentication, which allows an SIM-card subscriber

to be defined in or provided with the services on the LTE/SAE network without changing SIM

cards.

When a SIM-card subscriber sends an authentication request, the SAE-HSS can calculate and

generate RAND, SRES, and Kc, and then send them to the MME. After the authentication is

complete, the subscriber can access to the LTE/SAE network.

Enhancement

None

Dependency

The SAE-HSS implements this function independently, provided that the MME supports it.

2.1.2.11 WHFD-219901 Authentication Parameter Configurability Function

Availability

This feature has been available since SAE-HSS V900R006C03.

Specification

None.

Summary




Page 104 of 191

The authentication parameter configurability function enables the SAE-HSS to configure

non-standard values for the authentication parameters C1 to C5 and R1 to R5.

Benefits

For carriers

The USIM cards configured with non-standard C1 to C5 or R1 to R5 parameters can be

authenticated successfully

For subscribers

None.

Description

C1 to C5 and R1 to R5 parameters are customized to improve the security of authentication

algorithms shows the algorithm process.

Figure 1 MILENAGE algorithm process

Enhancement

None

Dependency

None.

2.1.3 WHFD-210210 Seamless Geographic Redundancy Solution of the HSS9860

Availability





Page 105 of 191

Specification

N/A

Summary

The HSS supports the seamless geographic redundancy solution, which allows the active and

redundancy HSSs to be deployed in different places and the FE and BE to be independently

deployed. When the subscriber data in the active HSS is modified, the updated data is sent to

the redundancy HSS in real time. Thus, data synchronization between the active and

redundancy HSSs is ensured. In addition, the periodic data check function is enabled to

ensure data consistency between the active and redundancy HSSs.

Benefits

For carriers

This function enables carriers to ensure higher reliability and security of the HSS. This

reduces the CAPEX and OPEX of carriers and enhances their competitive edge.

For subscribers

N/A

Description

The HSS supports three types of seamless geographic redundancy solution:

1+1 active/standby redundancy solution

The FE and the BE are integrated. Data synchronization between the two HSSs is

implemented over the data layer. In normal conditions, the active HSS provides all the

services, and the redundancy HSS does not provide services.

1+1 load-sharing redundancy solution

The FE and the BE are integrated. Data synchronization between the two HSSs is

implemented over the data layer. In this solution, both HSSs provide services and each

HSS backs up the data of the other one.

Redundancy solution for separated deployment of the FE and BE

The FE and the BE are separately deployed. The FEs and BEs of the two HSSs work in

active/standby or load-sharing mode.

The seamless geographic redundancy solutions supported by the HSS have the following

features:

Use dedicated IP channels to automatically synchronize dynamic and static data between

the active and redundancy HSSs in real time, and provide the data consistency check

function to ensure subscriber data consistency between the two HSSs.

Support automatic switchover between the HSSs to ensure uninterrupted service

processing.

Allow the FE and BE to be deployed in different places, which facilitates network

planning of carriers.

Enhancement

HSS9860V900R009C20 Enhancement:




Page 106 of 191

The redundancy HSS can accept and process the Diamter Request Message with

destination-host set to Hostname of active HSS. Also, when sending a Diamter Request

Message to peer device, such as MME, the redundancy HSS can set the destination-host as

the hostname of active HSS. That is, the redundancy HSS can act as if it is active HSS.

Dependency

The HSS9860 implements this function independently. There are no special requirements for

other NEs.

2.1.4 WHFD-210220 N+1 Compatibility Redundancy Solution

Availability


Specification

None.

Summary

The HLR supports the N+1 compatibility redundancy solution.

Benefits

For carriers

This feature enables carriers to provide redundancy for the HLRs provided by other

vendors. When an active HLR fails, the redundancy HLR immediately takes over the

services. This improves the reliability of the network.

For subscribers

None.

Description

In this solution, multiple active HLRs (the number of active HLRs is indicated by N) are

provided by other vendors, and the redundancy HLR is provided by Huawei. In normal

conditions, the active HLRs provide services, and the redundancy HLR is ready to take over

the services of the active HLRs. If multiple active HLRs fail, the redundancy HLR takes over

the services of the faulty active HLRs at the same time, provided that the total number of

subscribers in the active HLRs is smaller than the number of dynamic subscribers that the

redundancy HLR supports.

Enhancement

The enhancement of the N+1 compatibility redundancy solution enables the redundancy HLR

to synchronize the data from the active HLRs in real time. If an active HLR fails, the

redundancy HLR will immediately and automatically take over the services of the faulty

active HLR, thus ensuring that the service processing is not interrupted.

Dependency




Page 107 of 191

The implementation of this feature requires data configuration on the STP or MSC to set up

link connection to the redundancy HLR.

2.1.5 WHFD-210230 Automatic FE Switchover

Availability


Specification

None.

Summary

This feature enables the FE of the redundancy HLR to automatically take over the services

from the FE of the active HLR when the BE of the active HLR is faulty. In this case, the FE

of the redundancy HLR communicates with the local BE (that is, the BE of the redundancy

HLR), consuming less bandwidth in comparison to the situation when the FE of the faulty

active HLR communicates with the BE of the redundancy HLR over the bearer network.

Benefits

For carriers

This feature helps carriers to lower the bandwidth requirements and reduce the cost for

redundancy solutions.

For subscribers

None.

Description

In the seamless geographic redundancy solution, if the BE of the active HLR becomes faulty,

the FE of the active HLR accesses the BE of the redundancy HLR over the bearer network.

The communication between the FE and BE over the bearer network, however, requires high

bandwidth. To lower the requirement for bandwidth, the HLR provides the automatic FE

switchover feature, which allows the FE of the redundancy HLR to take over the services

from the FE of the active HLR when the BE of the active HLR becomes faulty. In this case,

the FE of the redundancy HLR communicates with the local BE, which consumes less

bandwidth

Dependency


NEs.

2.2 Features of the 2G/3G

2.2.1 WHFD-211000 CS Data Services

Availability




Page 108 of 191

These services are provided by the HLR9820 from V600.

Specification

3GPP29002

Summary

The HLR supports all standard circuit switch (CS) data services, including the facsimile

service, data CDA service, data CDS service, PAD access CA service, data PDS service, voice

and data alternative service, and telephony followed by data service.

Benefits

For carriers

These services enable carriers to provide diversified data services, thus satisfying the

requirements of telecommunication markets and enhancing their competitive edge.

For subscribers

Subscribers can obtain the most recent information resources anywhere at any time.

Description

The CS data services include the following services:

Facsimile service

− Alternate Speech and Facsimile Group 3 (TS 61)

− Automatic Facsimile Group 3 (TS 62)

Data CDA service

− Asynchronous duplex circuit data service working at 300 bit/s (BS21), 1200 bit/s

(BS22), 1200/75 bit/s (BS23), 2400 bit/s (BS24), 4800 bit/s (BS25), and 9600 bit/s

(BS26)

− Transparent/Non-transparent 3.1 kHz audio VF/UDI data service

Data CDS service

Packet access, synchronous non-transparent 3.1K audio /UDI working at 1200 bits/s

(BS31), 2400 bits/s (BS32), 4800 bits/s (BS33), and 9600 bits/s (BS34)

PAD access CA service

PAD access, circuit asynchronous, transparent/non-transparent 3.1k audio/UDI working

at 300 bits/s (BS41), 1200 bits/s (BS42), 1200/75 bits/s (BS43), 2400 bits/s (BS44),

4800 bits/s (BS45), and 9600 bits/s (BS46)

Data PDS service

Packet access, synchronous, UDI, non-transparent PDS service working at 2.4 kbits/s

(BS51), 4.8 kbits/s (BS52), and 9.6 kbits/s (BS53)

Voice and data alternative service (BS61)

Telephony followed by data service (BS81)

UMTS bearer service

− Asynchronous bearer service (BS20)

− Synchronous bearer service (BS30)

Enhancement

None




Page 109 of 191

Dependency

The HLR implements these services in compliance with standard protocols. The

implementation of these services requires the cooperation of the MSC and VLR.

2.2.2 WHFD-212000 GPRS Services

The General Packet Radio Service (GPRS) is developed on the basis of the existing GSM

system. The GPRS adopts packet switching functional entities in the GSM network to

implement transmission of packet data. It features real-time online, volume-based charging,

quick login, high transmission, and flexible switchover. The GPRS system, the expansion of

the GSM circuit switching system, enables mobile subscribers to access the Internet or other

packet data networks from the packet data mobile terminal.

The HLR supports the following GPRS functions:

2.5G GPRS (WHFD-212001)

3G GPRS (WHFD-212002)

Enhanced HSPA (WHFD-212003)

Support GPRS charging character (WHFD-212004)

2.2.2.1 WHFD-212001 2.5G GPRS

Availability


Specification

3GPP29002

3GPP22060

3GPP23060

3GPP29061

Summary

The packet data functions are implemented by using functional entities added in the GSM

network. The added functional entities comprise the GSM-GPRS network, provide bypass for

the data, and implement the GPRS service. The original GSM network implements the voice

function. In this way, the GPRS service is implemented without too many changes to the

GSM network. The added network functional entities include GGSN and SGSN. The GGSN

functions in a similar way as the GMSC, and the SGSN functions in a similar way as the

MSC/VLR.

The GPRS is mainly applied to E-mail service, Internet browsing, WAP service, e-commerce,

information query, and remote monitor.

Benefits

For carriers

This service enables carriers to manage the GSM and GPRS networks through one HLR,

thus saving the investment of carriers.

For subscribers

This service enables subscribers to access the Internet, send E-mails, browse the Internet,

enjoy e-commerce, and conduct remote monitoring anywhere at any time. Since the




Page 110 of 191

service charge is based on traffic volume, the subscribers can remain online all the time

without worrying about being charged based on time.

Description

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 and querying messages over interfaces.

The HLR supports 2G and 2.5G GRRS services. It allows the subscriber to access GSM or

GPRS network, or both of them.

Enhancement

None

Dependency


of this service requires the cooperation of the GGSN and SGSN.

2.2.2.2 WHFD-212002 3G GPRS

Availability


Specification

3GPP29002

3GPP22060

3GPP23060

3GPP29061

Summary

Compared with the GSM network, the UMTS network greatly accelerates the data

transmission, thus providing high-speed and more reliable GPRS services.

Benefits

For carriers

This service enables carriers to manage the GPRS and UMTS networks through one

HLR, thus saving the investment of carriers.

For subscribers

This service allows subscribers to enjoy high-speed GPRS services in the 3G network.

Description

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 and querying messages over interfaces.

The HLR supports the 3G GPRS service. Compared with the GSM GPRS service, the UMTS

GPRS service supports the extended QoS and the PDP charging characteristic, and provides

more powerful and excellent network services.




Page 111 of 191

Enhancement

None

Dependency



2.2.2.3 WHFD-212003 Enhanced HSPA

Availability


Specification

3GPP24008

Summary

The High Speed Downlink Packet Access (HSDPA) implements the high-speed downlink data

services in the UMTS network. At present, it is favored by carriers to develop high-traffic

mobile media services.

The High Speed Uplink Packet Access (HSUPA) aims to optimize the capacity and data

throughput in the uplink direction and minimize the delay in dedicated channels. The

enhanced HSPA specified in 3GPP defines a new transport channel to provide high-speed

uplink data services.

Benefits

For carriers

This service allows carriers to provide HSPA-based high-speed data services.

For subscribers

This service allows subscribers to enjoy high-speed uplink and downlink broadband

services.

Description

The HLR manages the subscription data of the HSDPA and HSUPA services, and sends the

subscription data to the SGSN when subscribers originate GPRS location update requests.

Enhancement

None

Dependency


of this service requires that the network supports the HSDPA and HSUPA services.

2.2.2.4 WHFD-212004 Support GPRS Charging Character

Availability





Page 112 of 191

Specification

3GPP29002

3GPP23060

3GPP 32215

3GPP 32015

Summary

The GPRS charging characteristics refer to the charging type adopted by a subscriber. The

method of generating CDRs varies according to the charging type.

Benefits

For carriers

This function allows carriers to specify different CDR generation methods for different

subscribers.

For subscribers

This function allows subscribers to choose a suitable charging service.

Description

The HLR9 supports the subscription of different charging characteristics and sends the

subscription data to the SGSN/GGSN. The charging characteristics supported by the HLR are

as follows:

NONE: no charging feature

HOT: hot charging, real-time charging

FLAT: flat charging

PREPAID: prepaid

NORMAL: ordinary charging

Enhancement

None

Dependency



2.2.3 WHFD-213000 Supplementary Services

The optional supplementary services include:

Call Waiting (CW)/Call Hold (CH)( WHFD-213001)

Multi-Party (MPTY)( WHFD-213002)

Unstructured Supplementary Service Data (USSD)( WHFD-213003)

Closed User Group (CUG)( WHFD-213004)

PLMN Specific Supplementary Services (PLMNSS)( WHFD-213005)

Calling name presentation (CNAP)( WHFD-213006)




Page 113 of 191

2.2.3.1 WHFD-213001 Call Waiting (CW)/Call Hold (CH)

Availability


Specification

3GPP29002

3GPP22083

3GPP23083

3GPP24083

Summary

The Call Waiting (CW) service allows the called party to receive a notification that another

party is trying to reach its number while the called party is engaged in an active call. The Call

Hold (CH) service allows a subscriber to place an existing active call on hold and answer

another incoming call.

Benefits

For carriers

This service can enhance the service provisioning capability of carriers and increase their

subscriber base. In addition, this service can improve call completion rate and improve

traffic volume.

For subscribers

This service can establish a call connection even when the called subscriber is busy. It

helps improve the call connection rate and thus enhances the subscriber satisfaction,

especially that of high-end subscribers and business subscribers.

Description

In the case of CW, the network informs the subscriber of another incoming call and requests

the subscriber to answer the call. The subscriber can determine whether to answer the call.

In the case of CH, the subscriber can establish a call connection to the second call and

alternate between the first call and the second call. The first call is placed on hold.

Generally, the CW and CH functions are used together. Therefore, the subscriber must

subscribe to the CW and CH services on the HLR. After the connection to a new call is

established, the subscriber needs to place the first call on hold so that the subscriber can

alternate between the first call and the second call.

Enhancement

None

Dependency



2.2.3.2 WHFD-213002 Multi Party SS(MPTY)

Availability




Page 114 of 191


Specification

3GPP29002

3GPP22084

3GPP23084

3GPP24084

Summary

The Multi-Party (MPTY) service allows a subscriber to make a conference call with multiple

subscribers. The participants of the conference call can talk with each other. The MPTY

service allows a maximum of six subscribers to talk with each other simultaneously. The

controlling subscriber of the conference call can add, disconnect, and isolate a remote

subscriber. The remote subscriber can communicate with the controlling subscriber but cannot

talk with other participants of the conference call.

Benefits

For carriers

This service allows carriers to provide a conference call solution to business subscribers,

which helps increase their subscriber base.

For subscribers

This service allows multiple subscribers to talk with each other in a simple conference

call.

Description

The MPTY service allows a subscriber to make a multi-connection call. That is, three or more

subscribers (participants) can communicate with each other at the same time. Huawei MSC

allows a maximum of six subscribers to participate in a conference call.

When an MPTY subscriber who is in conversation state answers a held call, the subscriber

can combine the two calls into an MPTY call through the MPTY service, and then talk with

the two callers at the same time.

The MPTY subscriber can perform the following operations:

Place the MPTY call on hold and resume it later.

Originate a new call, and place the MPTY call on hold.

In the case of an MPTY call and a single call, alternate between the two calls or add the

single call to the MPTY call.

Establish a private call connection with a remote subscriber. The call connection is

separate from the conference call.

Disconnect a remote subscriber.

Release an MPTY call.

Feature Enhancement

Before subscribing to the MPTY service, the subscriber must have subscribed to the CH

service.

Dependency




Page 115 of 191



2.2.3.3 WHFD-213003 Unstructured Supplementary Service Data (USSD)

Availability


Specification

3GPP29002

3GPP24090

Summary

The Unstructured Supplementary Service Data (USSD) service allows a subscriber to send a

service request to the network by typing a non-standard supplementary service operation

command in USSD format on the MS/UE. The USSD service also allows the network to send

USSD commands to the MS/UE to implement a service.

Benefits

For carriers

This service allows carriers to provide many value-added services, such as those

providing information related to stocks, lottery, weather forecast, and airline schedules.

Thus, it helps to enhance the service provisioning capability of carriers and increase their

subscriber base.

For subscribers

This service allows subscribers to obtain useful information related to stocks, lottery,

weather forecast, and airline schedules.

Description

Compared with the short message service, the USSD service can implement real-time short

message exchange. It is suitable for stock information query.

The HLR supports the USSD services of version 1 and version 2. It also sends the specified

USSD code to other NEs for further processing.

HLR support USSD code query of system level and subscriber level, we also support the

query according to the number range, that is, users of the same number range can use one

USSD code. HLR will map to different USSD center according to the USSD code and

number range.

Enhancement

None

Dependency


of this service requires the cooperation of the VMSC and SCP or USSD center.

2.2.3.4 WHFD-213004 Closed User Group (CUG)

Availability




Page 116 of 191


Specification

3GPP29002

3GPP22085

3GPP23085

3GPP24085

Summary

The Closed User Group (CUG) service allows one or more subscribers with the same

attributes to form a user group. The subscribers in the same group have the same calling

attributes. The CUG can be a small group consisting of few members or a large-sized

enterprise consisting of thousands of employees.

Benefits

For carriers

This service can enhance the service provisioning capability of carriers and attract

enterprise subscribers.

For subscribers

The subscribers within the CGU can enjoy flexible call rates.

Description

The CUG service enables subscribers, connected to a PLMN and other networks, to form

CUGs to and from which access is restricted. A subscriber can be a member of one or more

CUGs. The members of a CUG can communicate with each other but not, in general, with

users outside the group.

The attributes of the CUG are as follows:

CUG index: An ID assigned by the network to identify a CUG and used by the MS/UE.

CUG Interlock Code (IC): A code used by the network (not by the MS/UE) to identify

CUG membership.

Preferential CUG: When the CUG index is unavailable, the preferential CUG is used as

the default CUG index.

Inter-group incoming call allowed: The subscribers in the CUG with this attribute are

allowed to receive calls from the subscribers outside the CGU.

Inter-group outgoing call allowed: The subscribers in the CUG with this attribute are

allowed to originate calls to the subscribers outside the CGU.

Intra-group incoming call prohibited: The subscribers in the CUG with this attribute can

only originate calls to other subscribers in the CGU.

Intra-group outgoing call prohibited: The subscribers in the CUG with this attribute can

only receive calls from other subscribers in the CGU.

CUG call: A call originated in the same CUG or between CUGs.

Enhancement

None

Dependency




Page 117 of 191



2.2.3.5 WHFD-213005 PLMN Specific Supplementary Services (PLMNSS)

Availability


Specification

3GPP29002

Summary

The PLMN Specific Supplementary Services (PLMNSS) allow a subscriber to use the

supplementary services customized by carriers, such as Customized Ring Back Tone (CRBT)

and hot billing services.

Benefits

For carriers

This service facilitates the deployment of new services and reduces the service

development cost.

For subscribers

None.

Description

The HLR supports the subscription of the PLMNSS. The value of the PLMNSS code ranges

from 241 to 245. During the location update, the HLR sends the PLMNSS subscription data

to the MSC/VLR through standard information element (IE). If carriers plan to introduce a

new service, they only need to define the PLMNSS code of the new service, and then develop

the service on the MSC/VLR.

Feature Enhancement

The HLR allows you to flexibly configure the delivery mode of the PLMNSS code; that is,

the HLR supports the following modes:

Delivering the PLMN-SS code in the ISD procedure

Delivering the PLMN-SS code with the MSRN in the SRI procedure

Delivering the PLMN-SS code with the MSRN/FTN in the SRI procedure

Dependency



2.2.3.6 WHFD-213006 Calling Name Presentation (CNAP)

Availability


Specification




Page 118 of 191

3GPP29002

Summary

The service displays the caller’s contact information to the callee.

Benefits

For carriers

Carriers can provide value-added services to subscribers. The CNAP service helps to

improve customer satisfaction.

For subscribers

Callees can obtain the detailed information about callers..

Description

The Calling Name Presentation (CNAP) service is a supplementary service provided to the

callee. It is similar to the Calling Line Identification Presentation (CLIP) service. When the

subscriber, who has the CNAP service active, is called, the MSC serving the callee obtains the

contact information of the caller from the contact information database and displays the

contact information to the callee.

The contact information database stores the contact information of subscribers, such as the

subscriber name.

Feature Enhancement

None

Dependency



2.2.4 WHFD-214000 CAMEL Services

The Customized Applications for Mobile Network Enhanced Logic (CAMEL) is a set of

intelligent network (IN) solution designed to work on a GSM or WCDMA network.

CAMEL allows the WCDMA network to provide services that are independent of the existing

network. It allows carriers to provide new services over the existing network infrastructure.

The CAMEL is considered as a new network feature rather than a new supplementary service.

In a CAMEL mobile network, the carrier can provide customized services for subscribers

even if the subscribers roam out of the home network.

The CAMEL development consists of four phases, that is, CAMEL phase 1, CAMEL phase 2,

CAMEL phase 3, and CAMEL phase 4.

The four CAMEL phases support different applications:

CAMEL phase 1: It is applicable to the services related to MO/MT calls.

CAMEL phase 2: It is applicable to the services related to the supplementary service

invocation.

CAMEL phase 3: It is applicable to the SMS MO service, GPRS sessions, PDP context,

HLR subscriber data control, and network signaling load.




Page 119 of 191

CAMEL phase 4: It is applicable to the SMS MT service.

The CAMEL service of higher version encompasses the subscription data of lower version.

The HLR supports the four CAMEL versions.

2.2.4.1 WHFD-214100 CAMEL Phase 2

Availability


Specification

3GPP29002

3GPP23078

Summary

The CAMEL is a network feature and is incorporated into the GSM and IN network entities.

When a CAMEL subscriber roams or serves as the called party, the CAMEL data is

transmitted between the HPLMN and the VPLMN to trigger the IN services of the subscriber.

Benefits

For carriers

The HLR supporting the CAMEL allows the subscriber to subscribe to the IN service

immediately and makes IN service configuration more flexible. The CAMEL enables

carriers to add new services and new features more flexibly and conveniently. In addition,

carriers can use the features provided by the existing IN network, such as the familiarity

number service, pre-paid service, and message station service. This feature also reduces

the subsequent investment in equipment.

For subscribers

This feature allows subscribers to enjoy various IN services provided by the HLR, such

as familiarity number, message station service, and advice of charge.

Description

The HLR supports the following CAMEL-related functions:

Provides the MAP interface to connect to the gsmSCF.

Supports CAMEL phase 1 and CAMEL phase 2.

Supports the subscription of O-CSI, T-CSI, SS-CSI, and TIF-CSI data.

Enables the CAMEL subscriber who has subscribed to the U-CSI or UG-CSI data to

interact with the HLR in 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 feature requires the support from the network entities in

the IN network, including SSP, SCP, and SCF.

The intelligent subscription items of CAMEL phase 2 include:

Originating CAMEL Subscription Information (O-CSI) (WHFD-214101)

Terminating CAMEL Subscription Information (T-CSI) (WHFD-214102)

Supplementary Service Invocation Notification CAMEL Subscription Information

(SS-CSI) (WHFD-214103)




Page 120 of 191

Translation Information Flag CAMEL Subscription Information (TIF-CSI)

(WHFD-214104)

USSD CAMEL Subscription Information (U-CSI) (WHFD-214105)

USSD General CAMEL Subscription Information (UG-CSI) (WHFD-214106)

Enhancement

None

Dependency




Availability


Specification

3GPP29002

3GPP23078

Summary

The HLR supports the services of CAMEL phase 3.

Benefits

For carriers







For subscribers



Description

On the basis of CAMEL phase 2, CAMEL phase 3 supports the following services:

O-CSI (WHFD-214201)

T-CSI (WHFD-214202)

SS-CSI (WHFD-214203)

TIF-CSI (WHFD-214204)

U-CSI (WHFD-214205)

UG-CSI (WHFD-214206)

GPRS CAMEL Subscription Information (GPRS-CSI) (WHFD-214207)

Short Message Service CAMEL Subscription Information (SMS-CSI) (WHFD-214208)




Page 121 of 191

Dialed Service CAMEL Subscription Information (D-CSI) (WHFD-214209)

Mobility Management CAMEL Subscription Information (M-CSI) (WHFD-214210)

VMSC Terminating CAMEL Subscription Information (VT-CSI) (WHFD-214211)

Enhancement

None

Dependency




Availability


Specification

3GPP29002

3GPP29078

Summary

The HLR supports the services of CAMEL phase 4.

Benefits

For carriers







For subscribers



Description

In addition to the services of CAMLE phase 3, CAMEL phase 4 supports the following

services:

Mobile-Originated Short Message Service CAMEL Subscription Information

(MO-SMS-CSI) (WHFD-214301)

Mobile-Terminated Short Message Service CAMEL Subscription Information

(MT-SMS-CSI) (WHFD-214302)

Enhancement

None

Dependency




Page 122 of 191



2.2.5 WHFD-215000 Other Services and Functions

Other services and functions are:

Call Forwarding Default (CFD) (WHFD-215001)

Automatic Device Detection (ADD) (WHFD-215003)

Location Service (LCS) (WHFD-215004)

SMS Call Forwarding (WHFD-215005)

2.2.5.1 WHFD-215001 Call Forwarding Default (CFD)

Availability


Specification

None.

Summary

The Call Forwarding Default (CFD) service is a special service provided by the HLR. The

implementation of the CFD service does not require the cooperation with the MSC/VLR.

Benefits

For carriers

After a subscriber has the CFD service activated, almost all the calls to the subscriber

can be connected. At least, the calls can be connected to the FTN (such as the voice

mailbox) specified by the CFD service. In this way, the call completion rate of the

overall network can be improved substantially. In addition, the CFD service has greatly

simplified the configuration of call forwarding services. If a subscriber wants to forward

all the calls to the same number, you can specify an FTN during the provisioning of the

CFD service. Thus, you do not have to configure the FTN for every conditional call

forwarding service separately.

The CFD service allows carriers to provide powerful and flexible call forwarding

function for subscribers. It also helps carriers to enhance their competitive edge.

For subscribers

If a subscriber has registered the CFD service, almost all the calls to the subscriber can

be connected. At least, the calls can be connected to the FTN (such as the voice mailbox)

specified by the CFD service. This ensures smooth communication for subscribers.

Description

The CFD is supplementary to the conditional call forwarding services CFB, CFNRy, and

CFNRc. As it is a non-standard supplementary service, it does not have any allocated

supplementary service code. Therefore, the registration and deregistration of the CFD service

can be performed only by carriers.

If a subscriber has activated the CFD service based on a basic service but does not have the

conditional call forwarding service activated based on the same basic service, the calls to the




Page 123 of 191

subscriber are forwarded to the FTN specified by the CFD service. This can ensure that every

call to the subscriber is connected.

A conditional call forwarding service is not activated in the following cases:

The subscriber has not subscribed to subscribe to the conditional call forwarding service.

The subscriber has not registered the conditional call forwarding service.

The subscriber has not activated the conditional call forwarding service.

Assume that subscriber A has registered and activated the CFD service; the registered FTN is

N1, which is the number of a voice mailbox, and subscriber A has not registered the CFB

service. When subscriber B makes a call to subscriber A, who is engaged in another call, the

call is forwarded to N1, that is, subscriber A's voice mailbox.

Enhancement

None

Dependency

The CFD service is a special service provided by the HLR. The interface involved in the CFD

service complies with standard protocols. There is no special requirement for the MSC/VLR.

2.2.5.2 WHFD-215003 Automatic Device Detection (ADD)

Availability


Specification

3GPP29002

Summary

The HLR provides the Automatic Device Detection (ADD) function provided that the ADD

server is deployed in the network. The ADD server stores the type and configuration of user

equipment (UE). If the HLR detects the change of the IMEISV, IMSI, or subscription data, it

sends the subscriber information and MS/UE information to the ADD server, which then

automatically sends the configuration data to the MS/UE.

Benefits

For carriers

This function simplifies the operations of the subscribers who use the data services, and

thus increases the customer satisfaction.

For subscribers

This function facilitates subscribers to use new services. Instead of conducting the

complex network setting, subscribers can use services directly after they change their

SIM or USIM cards or MSs/UEs. For example, the ADD function allows the GPRS

service data to be automatically set on the MS/UE before a subscriber uses the GPRS

service. As a result, subscribers are more willing to use new data services.

Description




Page 124 of 191

During the location update of a subscriber, the MSC sends the IMEISV of the subscriber

through 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 relevant configuration data to the MS/UE based on the type of the

MS/UE. (The ADD server stores and manages the configuration data of various types of

MS/UE, such as the configuration of the MMS and GPRS. It also allows the configuration

data to be automatically sent to the MS/UE.)

When detecting the change of the IMSI, MSISDN, IMEISV, or subscription data such as the

subscriber identity (pre-paid service subscriber or post-paid service subscriber), the HLR

sends the relevant modification information to the ADD server. The ADD server then updates

the configuration data of the MS/UE through the network.

Enhancement

None

Dependency

The HLR works with the ADD server to implement the ADD function. In addition, a

proprietary interface, namely, the SOAP interface, is required between the HLR and the ADD

server.

2.2.5.3 WHFD-215004 Location Service (LCS)

Availability


Specification

3GPP22071

3GPP23171

3GPP24030

3GPP25305

3GPP25923

3GPP29002

Summary

The Location Service (LCS) is a service that complies with the GSM standards. It functions

independently from any basic service.

Benefits

For carriers

With the development of the telecommunication market, the provisioning of the LCS

service is inevitable. Carriers should provide the LCS service as soon as possible to meet

the requirements of the market and enhance their service competitiveness.

For subscribers

The LCS allows subscribers to learn about their current location, and thus brings about

great convenience to the daily life.

Description




Page 125 of 191

The LCS service can identify the specific location of a subscriber based on the channel ID

(CID) or latitude and longitude. The SMLC is a network entity that implements the LCS

service. Different from the GPS, the LCS service capitalizes on the existing GSM network.

Carriers can provide the LCS service by deploying several LCS functional entities, without

many changes to the network.

The HLR supports the subscription of 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 service can be implemented 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 third-party application of the LCS is very mature, the subscriber can learn of

the current location at any time, or 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 learn of the whereabouts.

Enhancement

None

Dependency


of this service requires the cooperation of the GMLC, SMLC, MSC, and SGSN.

2.2.5.4 WHFD-215005 SMS Call Forwarding

Availability


Specification

3GPP29002

3GPP23039

3GPP23040

3GPP23041

3GPP24011

3GPP24012

Summary

Short messages are forwarded to a third party according to the requirements of the carriers,

network, or subscribers. This service is called Short Message Service Call Forwarding

(SMSCF).

Benefits

For carriers

The SMSCF service is a value-added and helps increase the receiving success rate of

short messages

For subscribers

After the system provides the SMSCF service to subscribers, subscribers can activate or

deactivate the service based on actual requirements. Therefore, subscribers can flexibly




Page 126 of 191

control the implementation of SMSCF and select the terminal and the place to receive

short messages. This improves the quality of short message receiving.

Description

HLRb serving the subscriber who has subscribed to the SMSCF service checks whether this

subscriber can receive and send short messages and whether the current short message should

be forwarded. If yes, HLRb simulates the SMSC to send an SMS route request to the HLRc

that serves the forwarded-to party. (If both the forwarded-to party and the forwarding party

belong to HLRb, this flow is implemented within HLRb.) After HLRc sends the location

information and IMSI of subscriber C to HLRb, HLRb sends a message to the SMSC. This

message contains the location information of subscriber C, instead of the location information

of subscriber B.

The SMSC sends the short message to subscriber C based on the IMSI and location

information of subscriber C in the message.

Forwarding short messages to a subscriber of other HLR

The message flow is as follows:

1. The SMSC sends the SendRoutingInfoForSm message to the HLR.

2. After HLRb receives the SendRoutingInfoForSm message, it checks the subscription information of subscriber B.

If subscriber B has subscribed to, registered, and activated the SMSCF service but the forwarded-to party is not a local HLR subscriber, HLRb sends the SendRoutingInfoForSm message to HLRc serving the forwarded-to party. In this message, MSISDN is the forwarded-to number.

3. HLRc sends the SendRoutingInfoForSMAck message to HLRb.

4. HLRb sends the SendRoutingInfoForSMAck message to the SMSC.

Enhancement

None

Dependency


of this service requires the cooperation of the SMSC.




Page 127 of 191

2.2.6 WHFD-216000 Mobility Services

The mobility services include Subscriber Information Services (WHFD-216100).

The Subscriber Information Services consist of:

Any Time Interrogation (WHFD-216101)

Provide Subscriber Information (WHFD-216102)

Any Time Modification (ATM) (WHFD-216103)

2.2.6.1 WHFD-216101 Any Time Interrogation (ATI)

Availability


Specification

3GPP29002

Summary

The Any Time Interrogation (ATI) is a standard protocol-compliant subscriber information

service.

Benefits

For carriers

This service allows carriers to adopt the call charge rate based on the location to which a

subscriber roams. It also helps carriers to enhance their competitive edge.

For subscribers

Subscribers can benefit from the area-specific call charges.

Description

This function enables the SCP to interrogate the HLR for the location and status information

of subscribers.

Enhancement

None

Dependency

The HLR implements this function in compliance with standard protocols. The

implementation of this function requires the cooperation of the MSC, VLR, and SCP.

2.2.6.2 WHFD-216102 Provide Subscriber Information (PSI)

Availability


Specification




Page 128 of 191

3GPP29002

Summary

The Provide Subscriber Information (PSI) is a standard protocol-compliant subscriber

information service.

Benefits

For carriers

This function allows carriers to obtain detailed location and status information of

subscribers to provide more powerful functions. For example, carriers can adopt the call

charge rates based on the cell to which a subscriber roams. Thus, this function helps

carriers to enhance their competitive edge.

For subscribers

Subscribers can benefit greatly from the area-specific call charges or enjoy better

network service.

Description

The HLR obtains the information about the current cell and the status information of the

subscriber from the VLR to which the subscriber roams. The HLR then sends the queried

information to the GMSC through the SRI response or sends the queried information to the

SCP through the ATI response.

Enhancement

None

Dependency


implementation of this function requires the cooperation of the MSC and VLR.

2.2.6.3 WHFD-216103 Any Time Modification(ATM)

Availability


Specification

3GPP29002

Summary

The Any Time Modification (ATI) is a standard protocol-compliant subscriber information

service. SCP send ATM message to modify the subscription data.

Benefits

For carriers

This function make carriers adopt the new service more quickly.

For subscribers

NA

Description




Page 129 of 191

This function enables the SCP to modify the following subscription data in HLR.

Activate or deactivate the BAOC and BAIC service.

Activate or deactivate the O-CSI, T-CSI and M-CSI service.

Activate or deactivate the ODBOC and ODBIC service.

Enhancement

None

Dependency


implementation of this function requires the cooperation of the SCP.

2.2.7 WHFD-217000 Networking Functions

The networking functions include:

Multi-SP (WHFD-217001)

TDM 2M Signaling Link (WHFD-217002)

MAP phase2+ (WHFD-217003)

SIGTRAN (WHFD-217004)

SCTP multi-homing (WHFD-217005)

Supporting FNR(Flexible Number Route) (WHFD-217006)

Supporting the IPv6 Protocol (WHFD-217007)

2.2.7.1 WHFD-217001 Multiple Signaling Points

Availability


Specification

None.

Summary

This function 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

expand the capacity of the links between the HLR and the neighboring NEs.

Benefits

For carriers

This function enables carriers to break through the link limitation and improve its

signaling processing capability of the HLR, without imposing additional requirements on

the neighboring NEs.

For subscribers

None.

Description




Page 130 of 191

Due to the limitations imposed by the MTP layer protocol, only a maximum of 16 signaling

links can be configured between two neighboring signaling points. When the number of

subscribers exceeds the limit, the 16 links between the HLR and a signaling point cannot meet

the requirements of signaling data transmission, thus causing link congestion.

The Multiple Signaling Points function allows you to configure a maximum of 16 signaling

points on an HLR. Consequently, the HLR can establish a maximum of 16 × 16 links with a

neighboring signaling point without imposing additional requirements on the peer entity, thus

meeting the requirements of signaling data transmission.

Enhancement

None

Dependency

The HLR implements this function independently. There is no special requirement for other

NEs.

2.2.7.2 WHFD-217002 TDM 2M Signaling Link

Availability


Specification

None.

Summary

Huawei HLR supports TDM 2 Mbit/s links.

Benefits

For carriers

This function enables carriers to reduce cost and simplify networking. In addition, if the

EIR does not support the multi-SP function, it is subject to the limitation of sixteen 64

kbit/s links. If the sixteen 64 kbit/s links cannot meet the traffic requirements, the 2

Mbit/s links are preferred.

For subscribers

None.

Description

With the increase in the capacity and processing capability of the HLR, the processing

capacity of a signaling link decreases due to congestion. The processing speed of a 2 Mbit/s

signaling link is 31 times that of a traditional No.7 signaling link. Therefore, the 2 Mbit/s

signaling link can address the challenges posed by heavy load on the HLR more effectively.

Enhancement

None

Dependency




Page 131 of 191


NEs.

2.2.7.3 WHFD-217003 MAP Phase2+

Availability


Specification

3GPP29002

Summary

Huawei HLR supports MAP phase2+.

Benefits

For carriers

This function enables carriers to provide the services that are based on MAP phase2+,

thus making more profits.

For subscribers

This function allows subscribers to enjoy the services that are based on MAP phase2+.

Description

MAP phase2+ is supplementary to the MAP protocol. It is intended to help carriers to develop

more GSM supplementary services and telecommunication services.

MAP phase2+ supports CSI-triggered IN services (including CAMEL phase 1 and CAMEL

phase 2), regardless of voice service or data service.

In addition, MAP phase2+ can help carriers to implement the LCS service.

Enhancement

None

Dependency



2.2.7.4 WHFD-217004 SIGTRAN

Availability


Specification

None.

Summary

Huawei HLR supports SIGTRAN, namely, IP networking. The HLR meets diversified

networking requirements. The signaling bearer between the HLR and other NEs can be TDM




Page 132 of 191

and IP. In addition, the signaling type is not subject to the limitation of the physical bearer

type, and thus can be selected flexibly.

Benefits

For carriers

This function enables carriers to reduce cost in the SG construction.

For subscribers

None.

Description

The HLR provides the M3UA adaptation function to implement the conversion between

MTP3/MTP2-based TDM bearer and SCTP/IP-based IP bearer for the MAP signaling. 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 implement the SG function over

M3UA, the SG entity must be configured with the MTP signaling point code.

The SIGTRAN function does not include the M2UA function.

Enhancement

None

Dependency


NEs. If the peer end adopts TDM for bearing No. 7 signaling, an SG must be adopted for

signaling conversion.

2.2.7.5 WHFD-217005 SCTP Multi-Homing

Availability


Specification

RFC2960

Summary

In IP networking, the HLR provides the SCTP multi-homing function, which improves the

reliability of the IP network.

Benefits

For carriers

This function can improve the reliability of the IP network.

For subscribers

None.

Description




Page 133 of 191

In IP networking, the HLR/HSS 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 located in 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.

Enhancement

HSS9860 provide SCTP multi-homing function for both HLR and SAE-HSS

Dependency



The SAE-HSS implements this function in compliance with standard protocols. The

implementation of this function. Implementing it, however, requires the cooperation of the

MME.

2.2.7.6 WHFD-217006 FNR(Flexible Number Route)

Availability


Specification

RFC2960

Summary

The Flexible Number Routing (FNR) feature enables the Home Subscriber Server (HSS) to

forward CS-domain Mobile Application Part (MAP) messages to the Home Location Register

(HLR), allowing carriers to provide long term evolution (LTE) services for 2G and 3G

subscribers without upgrading their HLRs.

Benefits

For carriers

This feature enables carriers to provide LTE services for 2G and 3G subscribers without

upgrading their HLRs. This maximizes carriers' return on investment..

For subscribers

This feature enables 2G and 3G subscribers to use LTE services without changing their

mobile station international ISDN numbers (MSISDNs) or international mobile

subscriber identities (IMSIs). This improves subscriber experience.

Description

All MAP messages to HLR should be forwarded to HSS firstly by STP, and then HSS will

forward the message to HLR based on its configuration or subscription.

HSS can forward MAP messages to the HLR based on IMSI prefix, MSISDN prefix or

individual subscriber.




Page 134 of 191

HSS can be configured to forward CS-domain messages only, PS-domain messages only,

or BOTH.

HSS can be configured to calculate the AVs authentication vectors for all domain

(CS/PS/EPS), or only EPS domain. If HSS is configured to calculate EPS domain AVs only,

HSS will forward MAP authentication message to HLR.

Enhancement

None

Dependency


implementation of this function requires the cooperation of the HLR.

2.2.7.7 WHFD-217007 Supporting IPv6

Availability

This function has been available since HSS9860 V900R008C20.

Specification

3GPP TS 29.272

Summary

This feature enables the HSS9860 to support the IPv6 address type.

Benefits

For carriers

The IPv6 address type is required when the IPv4 address resources is insufficient. HSS9860

support IPv6-based applications, which meet the demand of carriers to expand network

deployment.

For subscribers

None.

Description

The HSS9860 supports PDP-Type of IPv6 and IPv4v6.

The HSS9860 supports PDN-Type of IPv6 and IPv4v6.

The HSS9860 can process the messages that contain the IPv4 or IPv6 address type at the

Diameter signaling layer.

Enhancement

N/A

Dependency

None.




Page 135 of 191

2.2.8 WHFD-218000 Enhanced Functions

The enhanced functions include certain special services, such as the multi-MSISDN, hot

billing, voice ring back tone, and voice broadcast services.

2.2.8.1 WHFD-218001 VLR Regional Roaming Restriction Services

Availability


Specification

None.

Summary

The VLR Regional Roaming Restriction service is based on VLR/SGSN roaming list. Every

subscriber is configured with a VLR/SGSN roaming list.

Benefits

For carriers

This service allows carriers to provide the local communication service for the

subscribers or provide roaming restriction services for the subscribers individually, thus

enhancing their competitive edge.

For subscribers

The subscriber who has subscribed to this service can enjoy relatively low charge rate. If

carriers provide the roaming restriction service for subscribers individually, the

subscribers can specify their roaming areas.

Description

The VLR Regional Roaming Restriction service allows carriers to provide various roaming

restriction services flexibly. Without deploying any extra network equipment, carriers can

restrict the subscriber's roaming to certain specified VLRs or prevent the subscriber from

roaming to certain specified VLRs through the subscriber roaming restriction template in the

HLR.

The VLR Regional Roaming Restriction service supports template-based configuration. On

the HLR, carriers can specify certain VLR numbers, and define a roaming restriction template

containing these VLR numbers. When subscribing to the VLR Regional Roaming Restriction

service, the subscriber only needs to reference the template. This feature can greatly improve

the working efficiency of carriers.

The VLR Regional Roaming Restriction service is widely used for the local communication.

Carriers can define a roaming template that contains all the VLR numbers of the local

network. The subscriber who subscribes to the roaming template can roam only to the local

network (such as a city, a province, or an area).

To provide the VLR Regional Roaming Restriction service to a subscriber, carriers must

configure a VLR/SGSN roaming list for the subscriber. The list describes the roaming rules

(for example, whether roaming is allowed) and the default roaming rule.




Page 136 of 191

When a subscriber performs location update in the CS or PS domain, 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 determines whether the subscriber is allowed to roam to the area according to

the specified roaming rule. If the number of the VLR/SGSN cannot match any record in the

VLR/SGSN roaming list, the HLR uses the default roaming rule to determine whether the

subscriber is allowed to roam to the area.

Enhancement

None

Dependency

The HLR implements this service independently. There is no special requirement for other

NEs.

2.2.8.2 WHFD-218002 CAMEL Restriction Function

Availability


Specification

None.

Summary

The CAMEL Restriction service is a special service provided by the HLR. 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 procedure or the

SRI procedure fails, and the subscriber cannot access the network or serve as the called party.

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

certain specified CAMEL data to the MSC/SGSN. This helps prevent the problems described

here.

Benefits

For carriers

This service allows carriers to configure the subscriber-based CAMEL processing

capability on the HLR. Thus, carriers can provide more customized CAMEL services for

subscribers. This service helps carriers to enhance their competitive edge.

For subscribers

None.

Description

The HLR supports the CAMEL Restriction service. Carriers can configure the service on the

HLR to control whether it should send CAMEL data in a procedure.

The HLR provides the following CAMEL restriction solutions:

Selective Bypass




Page 137 of 191

This is a CAMEL-based selective bypass solution. When the called party passes the

selective bypass authentication, the HLR does not include the T-CSI information of the

subscriber's PPS service into the SRI response message.

SMS-CSI delivery restriction

The HLR determines whether to deliver the SMS-CSI based on the VLR or SGSN to

which a 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, and the subscriber can send short messages.

VLR-based outgoing call restriction

The HLR determines whether to deliver the outgoing call restriction data based on 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 not

allowed to originate calls.

Subscriber-oriented CAMEL service customization

When a subscriber roams outside the local network, the HLR determines whether to

deliver the O-CSI and T-CSI data based on the network compatibility and the CAMEL

agreement signed between carriers. For example, according to the basic service keys,

carriers can specify that:

− The CAMEL logic is triggered only when the subscriber roams to the specified areas.

− Whether the subscriber is allowed to access the network after the subscriber roams to

the areas where the CAMEL is not supported.

− Whether a call is allowed when the network serving the calling party does not support

the CAMEL.

Enhancement

None

Dependency


NEs.

2.2.8.3 WHFD-218003 TCSI Suppression Enhancement

Availability


Specification

None.

Summary

The HLR supports the enhanced TCSI suppression function. Carriers can configure the

service to determine whether the HLR should send the T-CSI data.

Benefits

For carriers

This service allows carriers to configure the subscriber-based CAMEL processing

capability on the HLR. Thus, carriers can provide more customized CAMEL services for

subscribers and enhance their competitive edge.




Page 138 of 191

For subscribers

None.

Description

The HLR supports the T-CSI suppression function. When a subscriber serves as the called

party, the HLR checks whether the subscriber roams to the local VLR. If yes, the SRI

response message does not contain the T-CSI flag. If no, the SRI response message contains

the T-CSI flag.

Enhancement

None

Dependency


NEs.

2.2.8.4 WHFD-218004 Supporting Multiple OP

Availability


Specification

None.

Summary

The operator variant algorithm configuration field (OP) is a parameter introduced for

authentication calculation when the MILENAGE algorithm is used. All the subscribers of a

carrier use the same OP to distinguish themselves from the subscribers of other carriers. At

present, the HLR allows a carrier to set multiple OPs.

Benefits

For carriers

This function allows different USIM cards to use different OPs, thus greatly enhancing

the security of the system.

For subscribers

Every subscriber can have his/her own OP. Consequently, the security of the USIM card

is further improved.

Description

OP is a parameter used in the UMTS authentication. Carriers can configure UMTIS

authentication algorithms by setting the OP. The OP is stored in the HLR/AuC and the USIM

card. The HLR supports multiple OPs. Different USIM cards in an HLR can use different

OPs.

Enhancement

None

Dependency




Page 139 of 191


NEs.

2.2.8.5 WHFD-218005 Hot Billing

Availability


Specification

None.

Summary

The HLR supports the Hot Billing service, which is a customized supplementary service.

Benefits

For carriers

This service allows carriers to provide real-time billing services, such as the telephone

lease service.

For subscribers

Subscribers can obtain the call bill in real time and enjoy real-time billing services.

Description

If the subscriber has subscribed to the Hot Billing service, the MSC sends the original CDR

generated during the call to the iGWB. The iGWB then allocates a separate channel for the

final CDR and sends the final CDR to the billing center in real time for charging.

Enhancement

None

Dependency

This service is a non-standard service. The implementation of this service requires the

cooperation of Huawei MSC and VLR.

2.2.8.6 WHFD-218006 Alternative Line Service (ALS)

Availability


Specification

3GPP29002

Summary

The Alternative Line Service (ALS) allows a subscriber to have two different MSISDNs with

one MS/UE and one SIM/USIM card. The two MSISDNs are charged separately.

Benefits




Page 140 of 191

For carriers

This service helps carriers to increase their subscriber base and enhance their

competitive edge.

For subscribers

This service allows subscribers to apply for two numbers to make business calls and

private calls separately, without having to prepare two SIM cards.

Description

This service allows subscribers to make both business calls and private calls by using one

MS/UE and one SIM/USIM card. Therefore, the charging for the business calls and private

calls is performed separately.

The implementation of the ALS service requires the support from the MSC/VLR. In addition,

the MS/UE must support the configuration of line 1 and line 2.

The two MSISDNs of the ALS service have the following features:

The two MSISDNs map to line 1 and line 2 respectively. When a subscriber originates a

call, the MSISDN for the line through which the call is set up is displayed to the called

party.

The ALS service supports the activation of supplementary services for line 2 separately,

including call barring, call forwarding, and CW services.

The MSISDN of line 2 can only receive short messages. It cannot be used to send short

messages or perform USSD operations.

Enhancement

None

Dependency



2.2.8.7 WHFD-218007 HLR-Specific Roaming Restriction

Availability


Specification

None.

Summary

The HLR-specific roaming restriction function is based on the VLR/SGSN roaming list. Once

being configured, the VLR/SGSN roaming list is effective for all the subscribers served by an

HLR.

Benefits

For carriers

This function is a system function provided by the HLR and is effective for all the

subscribers in the HLR. It allows carriers to configure roaming restriction more flexibly.




Page 141 of 191

For subscribers

None.

Description

The HLR-specific roaming restriction function configures a VLR/SGSN roaming list for the

HLR. In addition, 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 uses the roaming rule to determine whether the subscriber is

allowed to roam. If no, the HLR uses the default rule to determine whether the subscriber is

allowed to roam. The roaming restriction rule in the VLR/SGSN roaming list is valid to all the

subscribers served by the HLR.

Dependency


NEs.

2.2.8.8 WHFD-218008 SMC Address Filtering

Availability


Specification

None.

Summary

The HLR supports the filtering of messages from short message centers (SMCs) according to

an address list.

Benefits

For carriers

This function can prevent malicious attacks through short messages and reduce the load

of the HLR and the network.

For subscribers

None.

Description

You can configure an SMC address list on the HLR. The HLR can shield short messages from

the short message centers contained in the address list. This can prevent malicious attacks and

reduce the load of the HLR and the network.

Enhancement

None

Dependency




Page 142 of 191


NEs.

2.2.8.9 WHFD-218009 SCP Address Filtering

Availability


Specification

None.

Summary

The HLR supports the SCP address filtering function.

Benefits

For carriers

This function can prevent malicious attacks through short messages and reduce the load


For subscribers

None.

Description

You can configure an SCP address list on the HLR. The HLR can shield short messages from

the SCPs contained in the address list. This can prevent malicious attacks and reduce the load


Enhancement

None

Dependency


NEs.

2.2.8.10 WHFD-218010 CF-specific Black and White Lists

Availability


Specification

None.

Summary

The CF-specific black/white list function provided by the HLR allows you to control the CF

service registration of subscribers. This function is effective for all the subscribers served by

the HLR. You can configure call forwarding rules for the specified FTNs on the HLR. Based

on the configuration, the HLR controls whether a subscriber can register these FTNs.




Page 143 of 191

Benefits

For carriers

This function allows carriers to manage the CF registration of subscribers more flexibly

and prevent the registration of unauthorized numbers.

For subscribers

This function prevents subscribers from incurring financial loss resulting from

registration of unauthorized FTNs.

Description

The CF-specific black/white list function is effective for all the subscribers. Carriers can

specify FTN segments (including the start FTN and the end FTN) according to the actual

condition, and configure the call forwarding rule and the default call forwarding rule based on

the number segments. If the FTNs registered by a subscriber are within the number segments,

the HLR adopts the call forwarding rule. If not, the HLR uses the default call forwarding rule.

If the call forwarding rule or the default call forwarding rule prohibits the registration of the

FTNs, the registration fails.

Enhancement

None

Dependency


NEs.

2.2.8.11 WHFD-218011 Network Capability Configuration (NCC)

Availability


Specification

None.

Summary

The Network Capability Configuration (NCC) feature allows you to configure the capability

sets for the services and MAP operations supported by the VLR, so that the HLR can process

services and MAP procedures according to the capability sets, thus improving the network

compatibility.

Benefits

For carriers

This feature can improve the HLR's compatibility with the surrounding NEs, increase the

HLR's MAP operation success rate and efficiency, meet carriers' customized network

compatibility requirements, and facilitate the network deployment.

For subscribers

None.

Description




Page 144 of 191

The NCC feature is implemented based on the NCC template and the VLR/SGSN type; that is,

it is implemented by loading NCC templates to the VLR/SGSN Type table. A VLR/SGSN

number prefix corresponds to an NCC template. In the HLR, the handling of the following

situations varies according to the services supported by the VLR/SGSN and the MAP

operation capabilities:

Special services

Certain special services such as MPTY and PLMNSS are supported only by certain

VLRs. If the HLR intends to send the data of these special services to the VLR in the

location update procedure and subscriber data insertion procedure, the HLR queries the

VLR Type table according to the VLR number to obtain the corresponding NCC

template. Then, the HLR processes the services according to configuration data in the

template.

Matching between the VLR number and the VLR Type table

In the CS domain, the HLR and the VLR may support different MAP phases. When

performing MAP operations such as location update and subscriber data insertion, the

HLR queries the VLR Type table according to the VLR number to obtain the NCC

template and the MAP phase supported by the VLR. Then, the HLR processes data as

follows:

− If the HLR receives the MAP message initiated by the VLR and the MAP phase in

the message is higher than that configured in the NCC template, the HLR performs

version negotiation.

− If the HLR initiates the MAP message, the HLR performs the MAP operation

according to the MAP phase supported by the VLR, which is defined in the NCC

template. This prevents version negotiation and saves link resources.

Matching between the SGSN number and the SGSN Type table

In the PS domain, the HLR and the SGSN may support different MAP phases. When

performing MAP operations such as location update and subscriber data insertion, the

HLR queries the SGSN Type table according to the SGSN number to obtain the NCC

template and the MAP phase supported by the SGSN. Then, the HLR processes data as

follows:

− If the HLR receives the MAP message initiated by the SGSN and the MAP phase in

the message is higher than that configured in the NCC template, the HLR performs

version negotiation.

− If the HLR initiates the MAP message, the HLR performs the MAP operation

according to the MAP phase supported by the SGSN, which is defined in the NCC

template. This prevents version negotiation and saves link resources.

Mismatching between the VLR number and the VLR Type table

In the CS domain, not all the VLR numbers are configured in the VLR Type table.

Sometimes, the HLR may fail to match the VLR Type table by using the VLR number.

In this case, a network compatibility failure occurs. Therefore, the HLR needs to provide

the default NCC template of the VLR. When the HLR fails to obtain the NCC template

because no matching record is found in the VLR Type table, the HLR processes the

services and MAP procedures according to the default NCC template.

Mismatching between the SGSN number and the SGSN Type table

In the PS domain, not all the SGSN numbers are configured in the SGSN Type table.

Sometimes, the HLR may fail to match the SGSN Type table by using the SGSN number.

In this case, a network compatibility failure occurs. Therefore, the HLR needs to provide

the default NCC template of the SGSN. When the HLR fails to obtain the NCC template

because no matching record is found in the SGSN Type table, the HLR processes the

services and MAP procedures according to the default NCC template.




Page 145 of 191

Enhancement

None

Dependency


NEs.

2.2.8.12 WHFD-218012 Ring Back Tone Service

Availability


Specification

None.

Summary

The Ring Back Tone (RBT) service allows subscribers to customize RBT to replace the

traditional RBT. When the RBT subscriber is called, the calling party hears the RBT

customized by the called party. The RBT can be the customized music or recorded voice.

Benefits

For carriers

This service can provide extra revenue for carriers and improve the subscriber

satisfaction.

For subscribers

This service allows subscribers to change the RBT flexibly and enables the calling party

to enjoy brilliant music or customized RBT.

Description

The RBT service is a service provided to the called party. It can play a piece of music or a

greeting subscribed by the called party to the calling party, instead of a common RBT.

After a subscriber subscribes to the RBT service, the subscriber can customize the RBT by

accessing a WWW or WAP site, or by dialing an access code. When an idle RBT subscriber is

called, the HLR plays a piece of music, DIY announcement, or video according to the calling

number, home area of the called party, and the time specified by the called party, instead of

the common RBT to the calling party.

Enhancement

None

Dependency


cooperation of MSC and VLR.

2.2.8.13 WHFD-218013 Local Mobile Station Identity (LMSI)

Availability




Page 146 of 191


Specification

None.

Summary

The HLR supports the Local Mobile Station Identity (LMSI) function, which is designed

especially for certain special areas. Certain services are provisioned in cooperation with the

satellite mobile telecommunication system. The HLR provides the LMSI function to facilitate

the provisioning of these services.

Benefits

For carriers

This function allows carriers to provide services in special areas under the help of the

satellite mobile telecommunication system. It also helps carriers to expand the service

coverage and enhance their competitive edge.

For subscribers

None.

Description

The basic process of the LMSI function is as follows:

The VLR sends the Location Area Code (LAC) of the subscriber to the HLR in the location

update procedure.

The HLR stores the received LMSI cells without any processing.

The HLR sends the LMSI cells to the VLR when initiating the PRN request.

With the LMSI function provided by the HLR, carriers can provide services in some special

areas under the help of the satellite mobile telecommunication system.

Enhancement

None

Dependency

The implementation of this function requires the cooperation of MSC and VLR.

2.2.8.14 WHFD-218014 Zone Code

Availability


Specification

3GPP29002

Summary

The HLR supports the Zone Code Roaming Restriction service, through which the

MSC/SGSN can narrow the roaming areas of a subscriber to cells.




Page 147 of 191

Benefits

For carriers

This service allows carriers to provide the local communication service for the

subscribers or provide roaming restriction services for the subscribers individually. It

also helps carriers to enhance their competitive edge.

For subscribers

The subscriber who has subscribed to this service can enjoy relatively low charge rate

and save the expense. If carriers provide the roaming restriction service for subscribers

individually, the subscribers can specify their roaming areas.

Description

The Zone Code Roaming Restriction service allows carriers to provide various roaming

restriction services flexibly. Compared with the VLR Regional Roaming Restriction service,

the Zone Code Roaming Restriction service allows carriers to narrow the roaming areas of a

subscriber to cells specified by the zone codes. A zone code identifies the areas planned for

implementing the roaming restriction service. A roaming area can be defined with a maximum

of 10 zone codes.

When a subscriber subscribes to the zone code, if the CC and NDC of the VLR/SGSN that

serves the subscriber are included in the subscription data, the HLR delivers the zone code list

to the VLR/SGSN. After the VLR/SGSN receives the zone code list, it restricts the roaming

according to the zone codes of the areas to which the subscriber roams. Roaming is restricted

if the zone code of the area to which the subscriber roams is not included in the zone code list.

Enhancement

None

Dependency


of this service requires the cooperation of the MSC, VLR, and SGSN.

2.2.8.15 WHFD-218016 CS Allocation/Retention Priority (CARP)

Availability


Specification

3GPP29002

Summary

The CS Allocation/Retention Priority (CARP) service allows carriers to set the priority for

subscribers during network congestion. It is valid to the subscribers only in the CS domain.

Benefits

For carriers

This service allows carriers to allocate different priorities to different subscribers and

thus provide voice services of different QoS for the subscribers accordingly. This service

also allows carriers to provide QoS solutions for the subscribers flexibly. When the




Page 148 of 191

network is congested, carriers can provide excellent voice service with short call

connection time, high voice quality, and high call completion rate for the high-end

subscribers. The line allocated to the low-end subscribers may be occupied or the voice

encoding rate of the line is decreased for attracting more high-end subscribers.

For subscribers

This service ensures that the high-end subscribers enjoy better voice and data services.

Description

The CARP service allows carriers to set the following priorities:

High priority (for subscribers of level 1)

Common priority (for subscribers of level 2)

Low priority (for subscribers of level 3)

Carriers can set subscriber priority for the access process and the service hold process

separately.

The HLR manages the CARP data of subscribers. The HLR sends the CARP data to the VLR

that serves the subscribers. Upon call setup, the VLR sends the CARP data to the RNC. The

RNC then provides differentiated services to the subscribers based on the CARP priorities.

Enhancement

None

Dependency



2.2.8.16 WHFD-218017 PS Allocation/Retention Priority (ARP)

Availability


Specification

3GPP29002

Summary

The PS Allocation/Retention Priority (ARP) service allows carriers to set the priority for

subscribers during GPRS network congestion. It is valid to the subscribers only in the PS

domain.

Benefits

For carriers

This service allows carriers to allocate different priorities to different subscribers and

thus provide voice services of different QoS for the subscribers accordingly. This service

also allows carriers to provide QoS solutions for the subscribers flexibly. When the

network is congested, carriers can provide excellent voice service with short call

connection time, high voice quality, and high call completion rate for the high-end

subscribers. The line allocated to the low-end subscribers may be occupied or the voice

encoding rate of the line is decreased for attracting more high-end subscribers.




Page 149 of 191

For subscribers

This service ensures that the high-end subscribers enjoy better voice and data services.

Description

The ARP service allows carriers to set the following priorities:

High priority (for subscribers of level 1)

Common priority (for subscribers of level 2)

Low priority (for subscribers of level 3)

Carriers can set subscriber priority for the access process and the service hold process

separately.

The HLR manages the ARP data of subscribers. The HLR sends the ARP data to the SGSN

that serves the subscribers. Upon call setup, the SGSN sends the ARP data to the RNC. The

RNC then provides differentiated services to the subscribers based on the ARP priorities.

Enhancement

None

Dependency



2.2.8.17 WHFD-218018 Global Tracing Function

Availability


Specification

3GPP29002

3GPP TS 32.422

Summary

To rectify a fault in the increasingly-complex telecommunication network, you need to

identify the root cause of the fault, analyze the root cause, and then rectify the fault

accordingly. The global network tracing function allows you to trace and collect information

about the specified subscriber at minimum consumption of system resources. With this

function, the maintenance personnel can pinpoint a fault to a specific NE, analyze the cause of

the fault, and then rectify the fault.

Benefits

For carriers

This function enables the maintenance personnel to pinpoint a fault in a network to a

specific NE, and then rectify the fault. It helps carriers to improve the fault handling

efficiency.

For subscribers

None.




Page 150 of 191

Description

The global network tracing function enables the network to trace the network entities in the

case of certain special events and obtain the call-related information. This function complies

with the GSM 12.08 protocol.

The HLR supports the global network tracing function. 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 that serves a subscriber to trace the subscriber. The MSC records the information

about the actions of the traced subscriber (such as location update, MS power-on/off, call

origination/termination, and short message origination/termination) in a tracing file, and

stores the file in the BAM. Thus, the maintenance personnel can locate failures by reading the

tracing file.

Enhancement

HSS9860 also support EPS domain-based global tracing function

Dependency



2.2.8.18 WHFD-218019 Video Fallback

Availability


Specification

3GPP23172

3GPP23018

Summary

The HLR supports the video fallback function.

Benefits

For carriers

This function can automatically convert a video call into a common call when the

conditions of a video call cannot be met. It can improve the call completion rate between

3G subscribers and the subscriber satisfaction.

For subscribers

This service can automatically convert a video call into a common call when the

conditions of a video call cannot be met, thus simplifying the subscribers' multimedia

service operations.

Description

The HLR complies with the 3GPP 23.172 and 23.018 protocols. The HLR also supports the

multimedia service fallback function. When a subscriber originates a multimedia call, the

network automatically converts the call into a common call in the following cases:




Page 151 of 191

The MS/UE of the called party does not support VP calls.

The called party refuses to answer the call in VP mode.

The called party has not subscribed to the VP service.

The called party roams to a GSM network.

During the VP call, the calling or called party switches to a GSM network.

Enhancement

None

Dependency



2.2.8.19 WHFD-218021 USSD Barring

Availability


Specification

None.

Summary

The HLR supports the barring of the USSD operations.

Benefits

For carriers

This function enhances carriers' control over the USSD operations performed by

subscribers and ensures the interests of carriers.

For subscribers

None.

Description

The HLR allows you to determine whether to bar the subscriber's USSD operations by

configuring the global data. Assume that a subscriber has subscribed to a customized

supplementary service with the service code of PLMN-SS-1. If you want to bar the USSD

operations of the PLMN-SS-1 service, set the USSD_BAR (PLMN-SS barring) parameter to

PLMN-SS-1 during the global data configuration. Currently, the HLR supports the barring of

the USSD operations for 15 customized supplementary services, ranging from PLMN-SS-1 to

PLMN-SS-F.

Feature Enhancement

USSD stands for Unstructured Supplementary Service Data. For example, carriers provide the

RBT service to a subscriber and allow the subscriber to activate the RBT service through the

MS/UE. The subscriber's activation of the RBT service on the MS/UE is called a USSD

operation.

Dependency




Page 152 of 191


NEs.

2.2.8.20 WHFD-218022 2G/3G QoS Mapping

Availability


Specification

None.

Summary

The HLR supports the 2G/3G QoS mapping feature.

Benefits

For carriers

This feature enhances the network's compatibility.

For subscribers

None.

Description

In the GPRS location update procedure, if the SGSN carries the GPRS enhancement flag in

its message, it indicates 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 and then

sends the 2G data to the SGSN.

Enhancement

None

Dependency


NEs.

2.2.8.21 WHFD-218023 Dialing Identification Code (DIC)

Availability


Specification

None.

Summary

The HLR supports the Dialing Identification Code (DIC) service.

Benefits




Page 153 of 191

For carriers


competitive edge.

For subscribers

This service allows subscribers to learn about the charge of the calls destined for a

certain subscriber category.

Description

The DIC service allows a subscriber to query the charge of the calls destined for a certain

subscriber category, such as family, colleague, and classmate.

A DIC subscriber originates a call by dialing called number + # + dialing identification

code. Here, dialing identification code can be any number specified by the subscriber. The

charge of the calls to a subscriber category can be obtained according to the dialing

identification code in the Call Detail Record (CDR).

Enhancement

None

Dependency



2.2.8.22 WHFD-218024 Multimedia RBT

Availability

This service has been available since HLR9820 V900R003.

Specification

None.

Summary

The HLR supports the multimedia RBT service.

Benefits

For carriers


competitive edge.

For subscribers

This service allows subscribers to change their multimedia RBT flexibly, so that the

calling parties can enjoy customized video/audio services.

Description

The 3G network supports the high-speed video services. The multimedia RBT service is

developed based on the traditional RBT service. The multimedia RBT service allows

subscribers to customize the video or audio chips according to their favorites or requirements

to replace the traditional RBT. When these subscribers are called, the calling parties can view

the customized video or listen to the customized RBT.




Page 154 of 191

Enhancement

None

Dependency


NEs.

2.2.8.23 WHFD-218027 Enhanced Multi-Level Precedence and Pre-Emption

(eMLPP)

Availability


Specification

3GPP 22067

3GPP 23067

3GPP 24067

Summary

The enhanced Multi-Level Precedence and Preemption (eMLPP) service allows the network

to adopt different network resources allocation policies (the queuing policy and preemption

policy) based on subscriber priorities when the network resources are insufficient. In addition,

the service also enables the network to adopt different call connection setup flows and

resource allocation flows to meet the requirements for delay of calls with different priorities.

When network resources are sufficient, the eMLPP service plays a weak role because its

preemption capability cannot be fully used. When network resources are insufficient, the

eMLPP service plays an important role because it can help carriers to maximize benefits.

Benefits

For carriers

This service allows carriers to segment the subscriber base and differentiate service

offering to meet expectation from different subscriber groups. When network resources

are insufficient, the eMLPP service can help carriers to maximize benefits.

For subscribers

This service enables subscribers of different eMLPP priorities to enjoy differentiated

services.

Description

The eMLPP service is a supplementary service that complies with GSM 02.67, GSM 03.67,

and GSM 04.67 protocols. This service allows high-priority subscribers to enjoy faster call

setup. When the call resources are insufficient, high-priority calls can seize the resources

(A-interface circuits or trunk circuits) of low-priority calls. Thus, the high-priority calls can

be connected in precedence. This service helps carriers to provide differentiated services to

subscribers.




Page 155 of 191

The eMLPP service provides seven priorities: A, B, 0, 1, 2, 3, and 4. The two highest

priorities (A and B) are reserved for network internal use, for example, for emergency calls or

for specific Voice Broadcast Service (VBS) or Voice Group Call Services (VGCS). These two

priorities may only be used in the domain of one MSC/VLR. Priorities A and B are mapped to

level 0 for priority treatment outside the MSC area where they are applied. The other five

priorities are offered for subscribers and can be applied globally. If supported by all related

network elements, they can also be used for interworking with ISDN networks providing the

Multi-Level Precedence and Preemption (MLPP) service. A subscriber can be assigned a

highest priority and a default priority. The default priority cannot override the highest priority.

If the MS/UE supports the modification of the eMLPP priority, A subscriber can modify the

default priority through the MS/UE. During a location update procedure, the HLR inserts the

highest priority and default priority to the VLR.

A subscriber can be assigned one or more priorities. The subscriber can select a priority for

each call within the authorized priorities. The network allocates resources to each call

according to the priority. In addition, the subscriber can select different call connection setup

modes for calls with different priorities.

The eMLPP service involves fast call connection setup and queuing & preemption.

Fast call connection setup

Whether to use fast call setup can be configured for a call of a certain priority.

Queuing & preemption

When the network resources (such as trunk circuits, signaling channels, and service

channels) are limited, the network holds calls of high priority and offers preferential

treatment for these calls in queuing, and even allows these calls to seize the resources of

low-priority calls.

Enhancement

None

Dependency


of this service requires the cooperation of the MSC, VLR, BSC, RNC, and MS/UE.

2.2.8.24 WHFD-218028 Multi IMSI Multi MSISDN (MIMM)

This service consists of the following services:

WHFD-218034 Multiple MSISDN Service

WHFD-218035 Multiple IMSI service

2.2.8.24.1 WHFD-218034 Multiple MSISDN Service

Availability


Specification

None.




Page 156 of 191

Summary

The HLR supports the Multiple MSISDN solution.

Benefits

For carriers

This service enables carriers to increase their subscriber base and enhance their

competitive edge. Carriers can make flexible charging policies to attract subscribers, thus

making more profits.

For subscribers

This service enables subscribers to use one card and multiple MSISDNs according to

their requirement. By using different MSISDNs in different regions, subscribers can

enjoy the local charging policy while roaming.

Description

The HLR9820 supports the Multiple MSISDN solution that allows a subscriber to be

provided with an IMSI and 32 MSISDNs. It is applicable to subscribers who need to use

different MSISDNs on one MS/UE. For example, a subscriber can use one MSISDN at work

and another MSISDN at home, or different MSISDNs in different countries (local numbers in

several locations, so that callers can save long-distance charges.):

Multiple MSISDN numbers (one master, others slave), all MSISDNs can receive call and

SMS, but only master MSISDN can make originated call and originated SMS.

Subscribers can use USSD command to switch master MSISDN and slave MSISDN.

Enhancement

None

Dependency

The implementation of this service requires the cooperation of the MSC and VLR.

2.2.8.24.2 WHFD-218035 Multiple IMSI Service

Availability

This service has been available since HLR9820 V900R003 and HLR9820 V900R006C06.




Page 157 of 191

Specificationy

None.

Summary

The Multiple IMSI service enables a subscriber to use different SIM cards that are associated

with the same MSISDN.

Benefits

For carriers

Carriers can provide flexible charging policies to attract more subscribers, increase revenue,

and enhance their competitive edge.

For subscribers

Subscribers can benefit as follows:

− Use the same MSISDN to make calls on different terminals, such as mobile stations

(MSs), vehicle-mounted stations, and wireless fixed stations.

− Use the same MSISDN to request both the circuit switched (CS) and packet switched

(PS) services on different MSs. For example, use one MS to make voice calls and the

other to surf on the Internet.

− Use the same MSISDN to access services on both the 2G and 3G networks.

− Share the same MSISDN among their family members.

− Provide a uniform Enterprise access number for customers.

Description

The HLR supports the Multiple IMSI service by allowing a subscriber to use the same

MSISDN associated with a maximum of nine SIM cards. Each card is configured with its

own authentication data and dynamic data, and can be used to initiate calls, receive calls, or

only receive short messages. The SIM card connection sequence can be modified using the

unstructured supplementary service data (USSD) function.

The Multiple IMSI service is categorized into the one live service, main/auxiliary card service,

simultaneous ringing service, and sequential ringing service.

One live service: Among the SIM cards that are associated with the same MSISDN, only

one SIM card is allowed to request services each time. When a subscriber performs a

location update using a SIM card, the HLR updates the subscriber location and sends a

CANCEL LOCATION message to all the other SIM cards that have accessed the

network.

Main/auxiliary card service: When a call is placed to a Multiple IMSI subscriber, the call

is connected to only the SIM card that has the highest call connection priority among all

the other SIM cards that are associated with the same MSISDN.

Simultaneous ringing service: When a call is placed to a Multiple IMSI subscriber, the

call is connected to all the MSs with the registered SIM cards. All the MSs ring

simultaneously until the subscriber answers the call on an MS.

Sequential ringing service: When a call is placed to a Multiple IMSI subscriber, the call

is connected to the MSs with the registered SIM cards based on the configured

connection sequence. The MSs ring in sequence until the subscriber answers the call on

an MS or the connection to all the MSs fails.




Page 158 of 191

Dependency

The implementation of this service requires the cooperation of the MSC and VLR. The

simultaneous ringing service and sequential ringing service require support from Huawei

MSC and Huawei VLR.

2.2.8.25 WHFD-218030 CCBS Service

Availability


Specification

None.

Summary

The HLR supports the Completion of Calls to Busy Subscriber (CCBS) service.

Benefits

For carriers

This service enables carriers to increase their subscriber base, enhance their competitive

edge, and make more profits.

For subscribers

This service enables subscribers to enjoy more call services.

Description

If subscriber A, who has the CCBS service active, calls subscriber B who is in the

network-determined busy state, the network automatically connects the call to B after B is

available. Therefore, A can communicate with B without dialing the number of B again.

The HLR adopts the SSAP protocol to implement the CCBS service. The following figure

shows the typical networking of the related NEs.




Page 159 of 191

The CCBS service procedure is as follows:

When subscriber A originates a call to subscriber B, GMSC b initiates an SRI procedure to

HLR b.

HLR b obtains the MSRN of subscriber B from MSC/VLR b and sends the MSRN of

subscriber B to GMSC b.

During the setup of the call, it is found that subscriber B is busy. GMSC b sends MSC/VLR a

a message, indicating that subscriber B is busy.

MSC/VLR a sends a message to subscriber A, asking whether to activate the CCBS service.

If subscriber A activates the CCBS service, MSC/VLR a informs MSC/VLR b of the service

activation through HLR b by using the SSAP protocol.

When subscriber B becomes available, MSC/VLR b sends MSC/VLR a a message, which

indicates that subscriber B is available, through HLR b by using the SSAP protocol.

The network has a call automatically originated to subscribers A and B.

Enhancement

None

Dependency

This service is a private service provided by Huawei. The implementation of this service

requires the cooperation of Huawei MSC/VLR. There is no special requirement for the

MS/UE.

2.2.8.26 WHFD-218031 ACR Service

Availability


MS a MS b

MSC/VLR a GMSC b MSC/VLR b

ISUP/BICC ISUP/BICC

SSAP

MAP

MA

P

SS

AP

HLR b




Page 160 of 191

Specification

None.

Summary

The Anonymous Call Rejection (ACR) service allows subscribers provided with the CLIP

service to reject the calls from subscribers provided with the Calling Line Identification

Restriction (CLIR) service.

Benefits

For carriers

This service enables carriers to increase their subscriber base, enhance their competitive

edge, and make more profits.

For subscribers

The subscriber can reject the anonymous calls automatically. Fraud or annoy caused by

anonymous calls can be avoided.

Description

The HLR provides the following ACR-related functions:

Configuration of the ACR SS code

Provisioning, withdrawal, and query of the ACR service

Mobile subscribers can activate, deactivate, and query the ACR service through USSD

operations on their MSs/UEs.

Before subscribing to the ACR service, the subscriber must have subscribed to the CLIP

service. When a subscriber provided with the ACR service receives a call originated from a

CLIR subscriber, the HLR returns an SRI response containing the ACR SS code to the GMSC.

Based on the ACR SS code contained in the SRI response, the GMSC rejects the call.

Enhancement

None

Dependency



2.2.8.27 WHFD-218032 Subscriber-Level Service Control Function

Availability


Specification

None.

Summary

The HLR supports the subscriber-level service control function. It allows service control of

subscribers based on location areas.




Page 161 of 191

Benefits

For carriers

This function helps carriers to improve network security and also meets the customized

requirements of carriers.

For subscribers

None.

Description

The HLR provides the subscriber-level service control function.

On the HLR, carriers can set whether to allow a subscriber to originate calls, send short

messages, receive messages, access networks through the GPRS in each VLR/SGSN. When a

subscriber is roaming, the HLR delivers the mapping service capability set based on the

roaming area of the subscriber.

Enhancement

None

Dependency



2.2.8.28 WHFD-218033 SMS Rerouting

Availability


Specification

3GPP 23.840

Summary

The Short Message Service (SMS) Rerouting service enables short messages to be routed to

the SMS Router located on the HPLMN and then delivered to subscribers. The SMS-Router

rejects junk short messages and delivers only valid short messages to subscribers.

Before providing the SMS Rerouting service for subscribers, enable the HLR to support this

service. The HLR determines whether to enable this service based on the system

configuration, service subscription, and GT of the short message service center (SMSC) that

interworks with the HLR.

Benefits

For carriers

Short messages that may have risks on national security are rejected.

For subscribers

None.

Description




Page 162 of 191

SMS Router HLR SMS_GMSC

MAP_SRI_FOR_SM req

MAP_SRI_FOR_SM req

MAP_SRI_FOR_SM req

MAP_SRI_FOR_SM rsp

MAP_SRI_FOR_SM rsp

MAP_SRI_FOR_SM rsp

Message flow of the SMS Rerouting service

1. Upon receiving a MAP_SRI_FOR_SM req message from the SMSC, the HLR forwards the

message to the SMS Router.

2.The SMS Router sends a MAP_SRI_FOR_SM req message to the HLR, and the HLR returns

a MAP_SRI_FOR_SM rsp message to the SMS Router. The response message contains the

MSC number or the SGSN number.

3.The SMS Router sends a MAP_SRI_FOR_SM rsp message to the SMSC. The SMSC delivers

short messages to the SMS Router, and the SMS Router then delivers the short messages to

subscribers.

Dependency

The implementation of this feature requires the cooperation of the HLR and the SMS Router.

2.2.8.29 WHFD-218036 Monitor of Call Forwarding Registration

Availability


Specification

None

Summary

HLR count the Call Forwaring Registration of each user,.If the counted times in the

configured periods exceed the configured times, HLR will record a alarm file.

Benefits

For carriers

Monitor the user behavior of Call Forwaring Registration, prevent the network is used

for fraud.

For subscribers

None.

Description




Page 163 of 191

HLR count the Call Forwaring Registration of each user, If the forward-to-number is a

international number, the RegistrationTimes will plus one. If the Registration Times in the

configured periods exceed the configured times, HLR will record a alarm file.

Dependency


NEs.

2.2.8.30 WHFD-218037 Multi-Call

Availability


Specification

3GPP 24135

3GPP 29002

Summary

When both the MS of a subscriber and the network support the Multi-Call (MC) service, the

subscriber can set up multiple ongoing calls in the Circuit Switched (CS) domain. The

number of calls is jointly determined by the parameters set on the MS, mobile network and

the parameters set by the carrier and the subscriber. A maximum of seven calls can be set up.

Each call has its own bearer, but the conversation can be held only on one bearer at a time.

The MC service is applicable to all bearer services. The MC service is provisioned by the

carrier and subscribers can activate or deactivate this service by using the MSs.

Benefits

For carriers

Carriers can provide the MC service as a value-added supplementary service for

subscribers.

For subscribers

When both the MS of a subscriber and the network support the MC service, the

subscriber can set up multiple ongoing calls in the CS domain. The number of calls is

jointly determined by the parameters set on the MS, mobile network and the parameters

set by the carrier and the subscriber. A maximum of seven calls can be set up.

Description

The HLR provides the MC service to subscribers. On the HLR, Maximum MC attempts

allowed and User determined maximum MC attempts must be set to specify the number of

calls that the subscriber can establish at the same time. The value of User determined

maximum MC attempts can be determined by subscribers on MSs through the

supplementary service registration flow. The value of User determined maximum MC

attempts cannot be greater than the value of Maximum MC attempts allowed.

The HLR sends the MC service data to the VLR upon location update, data restoration, and

modification of the MC service.

Dependency

The implementation of this feature requires the cooperation of the MSC.




Page 164 of 191

2.2.8.31 WHFD-218038 Preferred Roaming

Availability


Specification

3GPP 29002

Summary

The preferred roaming service enables a roaming subscriber to access the preferred PLMN

when multiple PLMNs are available at the same time.

Benefits

For carriers

Carriers can provide value-added services for subscribers and enhance the competitive

edge.

For subscribers

Subscribers can access preferred PLMNs, thus reducing call charge.

Description

On the HLR, you can set the preferred access mode for PLMNs and the service processing

rules for different IMSI prefixes. The PLMN is identified by the VLR/SGSN number prefix.

When a subscriber roams out of the home PLMN, the HLR identifies the PLMN to which the

subscriber is roaming based on the VLR/SGSN number prefix contained in the location

update request. The HLR then checks whether the subscriber is allowed to roam to this PLMN

based on the preferred access mode configured for the PLMN and the service processing rules

configured for the IMSI prefix.

The processing of the location update request varies according to the preferred access mode

configured for the PLMN and the service processing rules configured for the IMSI prefix.

If the preferred access mode is RESTRICTED, the HLR rejects the location update

request.

If the preferred access mode is PREFERRED and an IMSI prefix matching the

subscriber's IMSI prefix can be found, the HLR processes the service based on the rules

configured for the IMSI prefix. If a matching IMSI prefix cannot be found, the HLR

processes the service based on the default rules configured for the PLMN.

If the preferred access mode is ALLOWED, the HLR rejects the location update request

first and records the number of rejection times. When the subscriber attempts to access

the PLMN again, the HLR checks whether the number of rejection times reaches the

specified value.

Dependency


NEs.




Page 165 of 191

2.2.8.32 WHFD-218039 Welcome Message Service

Availability


Specification

3GPP 29002

Summary

The welcome message service allows a short message to be sent to roaming subscribers. The

short message may contain greetings, a brief introduction to the visited area, and other

information about the weather or hotels in the visited area.

Benefits

For carriers

The welcome message service helps to improve subscriber experience and customer

satisfaction.

For subscribers

Personalization services help to improve subscriber experience.

Description

When the location update request received by the HLR indicates that the serving VLR or

SGSN of the subscriber changes, the HLR sends a USSD message to the specified AS. The

location update requests include the GPRS location update requests. The USSD message

carries the IMSI and MSISDN of the subscriber, the original VLR or SGSN number, the

current VLR or SGSN number, and the HLR flag.

The AS determines whether to send a short message. It also determines the contents of the

message, for example, welcome greetings, farewell greetings, and information about the

weather, hotel information or scenery of the visited area. If a short message needs to be sent,

the AS constructs the short message based on the USSD message and then sends a message to

the short message center.

Dependency

The implementation of this feature requires the cooperation of the AS.

2.2.8.33 WHFD-218040 Mobile Terminating Roaming Retry Call

Availability


Specification

3GPP 23018

3GPP 29002

Summary




Page 166 of 191

The definition of this feature is when the mobile terminating subscriber having roamed from

the VMSC1 to an adjacent VMSC2 before the call connected successfully, the network

reroute the call to the VMSC2 again. The details read as follows: when the mobile subscriber

A is in the edge-crossing area of two or more VMSCs, the mobile station, subject to the radio

environment and so on, is prone to frequently initiate the inter-VLR location update procedure,

and if the mobile subscriber is called then, such a phenomenon may occur, e.g., the mobile

subscriber A is at the VMSC1 during an SRI procedure but after the VMSC1 having allocated

the MSRN and before the receipt of the paging response (including before and after paging),

the mobile subscriber A roams to the VMSC2 adjacent to the VMSC1, so the MT call toward

subscriber A under VMSC1 would fail, the VMSC1 will then notify the GMSC to initiate the

SRI procedure once again, and the call will be rerouted to the VMSC2 by the network, thus

the call completion rate will be improved.

Benefits

For carriers

This feature will improve the call completion rate in the edge-crossing areas of the

VMSCs, and thus improve the customer satisfaction.

For subscribers

This feature will improve the call completion rate in the edge-crossing areas of the

VMSCs, and thus improve the user perception.

Description

when the mobile subscriber A is in the edge-crossing area of two or more VMSCs, the mobile

station, subject to the radio environment and so on, is prone to frequently initiate the

inter-VLR location update procedure, and if the mobile subscriber is called then, such a

phenomenon may occur, e.g., the mobile subscriber A is at the VMSC1 during an SRI

procedure but after the VMSC1 having allocated the MSRN and before the receipt of the

paging response (including before and after paging), the mobile subscriber A roams to the

VMSC2 adjacent to the VMSC1.

At this moment, the VMSC2 initiates a Location Update procedure to HLR, and HLR send a

Cancel Location to VMSC1, the VMSC1 then notify the GMSC to initiate the SRI procedure

to HLR once again. HLR will delay the 2nd

SRI procedure until the Update Location

procedure finish.

Dependency

The implementation of this feature requires the cooperation of the GMSC and VMSC.

2.2.8.34 WHFD-218041 Location Update Billing

Availability


Specification

3GPP 29002

Summary

The Location Update Billing service enables the Home Location Register (HLR) to send a

Simple Object Access Protocol (SOAP) notification to a third-party device when a

subscriber's Visitor Location Register (VLR) changes because the subscriber roams outside




Page 167 of 191

the home public land mobile network (HPLMN) country and updates location in the circuit

switched (CS) domain. The notification contains the subscriber's international mobile

subscriber identity (IMSI), mobile station international ISDN number (MSISDN), the original

VLR number (the number of the VLR serving the subscriber before the location update), and

the new VLR number (the number of the VLR serving the subscriber after the location

update). The subscriber then can be informed of the charging information in the roaming

network through short messages.

Benefits

For carriers

Carriers can send the current charging information to subscribers when subscribers roam

outside their HPLMN countries.

For subscribers

Subscribers who roam outside their HPLMN countries can receive in-time charging

information from carriers.

Description

The following processes are added to the Location Update procedure: When a subscriber

roams outside the HPLMN country and successfully updates location in the CS domain, the

HLR checks whether the VLR number in the Update Location request is the same as that in

the HLR's dynamic database. If the VLR numbers are different, the HLR sends the

subscriber's IMSI, MSISDN, the original VLR number, and the new VLR number to the

provisioning gateway (PGW) through the MCI interface. The PGW then sends the SOAP

notification to a third-party device.

Dependency

The implementation of this feature requires the cooperation of the MSC and VLR.

2.2.8.35 WHFD-218042 Mobile terminating roaming forwarding (MTRF)

Availability

This feature has been available since HSS9860 V900R008C01.

Specification

3GPP TS 23.018

Summary

Mobile terminating roaming forwarding (MTRF) prevents paging failures caused by roaming

between two MSCs or fallback from an LTE network to a circuit-switched (CS) network..

Benefits

For carriers

MTRF increases the paging success rate and ultimately the call completion rate.

MTRF has a lower connection delay than mobile terminating roaming retry

(MTRR).




Page 168 of 191

For subscribers

MTRF improves subscriber experience by providing more reliable voice services.

Description

MTRF takes precedence over Super-Charger. To be specific, if the HLR is required to

send a cancel location message in MTRF but is not required to send a cancel location

message in Super-Charger, the HLR sends a cancel location.

MTRF applies to the scenarios where the UE detects that the MSC/VLR that sent the paging

message is not the serving MSC/VLR and initiates a location update to the serving MSC/VLR

when:

The called party is moving between MSCs while being paged.

The called party drops its LTE connection and falls back to a 2G or 3G network while

being paged.

Dependency

The HSS9860 implements this function in compliance with the standard protocol.The

implementation of this feature requires the cooperation of GMSC and VMSC.

2.2.9 WHFD-219000 Authentication Center Function(AUC)

The authentication function is defined according to a protocol and is implemented by the

Authentication Center (AuC). Incorporating the AuC function, the HLR supports 3GPP

standard authentication procedures and the relevant authentication encryption algorithms.

The HLR supports the KI encryption (WHFD-219200) function. To ensure the security, the KI

data is encrypted during its transfer from the card manufacturer to the carrier. The HLR

supports the loading of the encrypted KI data and stores the encrypted KI data in the database.

Meanwhile, the key is also encrypted to ensure the security of the KI data.

The HLR uses K4 as the key, and encrypts and decrypts KI data by using the DES or AES

algorithm. The subscriber can select different K4s for encrypting the KI.

2.2.9.1 WHFD-219100 Quintuplet-to-Triplet Conversion

Availability


Specification

3GPP29002

3GPP33102

Summary

When a subscriber holding the USIM card roams to a GSM network, the HLR converts the

calculated authentication quintuplets into authentication triplets, and sends the triplets to the

VLR/SGSN.




Page 169 of 191

Benefits

For carriers

This feature 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 to a 2G network, protecting the investment of carriers in

the 2G network.

For subscribers

This feature allows a 3G subscriber to roam to a 2G network and ensures smooth and

safe voice conversation.

Description

In the GSM network, the MSC/VLR performs subscriber authentication based on

authentication triplets. When a subscriber holding the USIM card roams to the GSM network,

the MSC/VLR sends an authentication request to the HLR/AuC. The HLR generates

authentication quintuplets according to the information stored in the USIM card and sends the

quintuplets to the MSC/VLR. If the MSC/VLR cannot process the quintuplets, the

authentication fails. After adding with the quintuplet-to-triplet conversion function, the

HLR/AuC converts the authentication quintuplets into authentication triplets and sends the

triplets to the MSC/VLR. In this way, the 3G subscriber can pass the authentication and roam

to the 2G network successfully.

Enhancement

None

Dependency




Issue V 1.0 (2014-01-22) Huawei Proprietary and Confidential Copyright

© Huawei Technologies Co., Ltd

Page 170 of 191

2.2.10 WHFD-220000 Machine to Machine communications(M2M)

2.2.10.1 WHFD-220001 M2M Terminal Information Sharing

Availability


Specification

None

Summary

M2M management platform query the location and status of M2M Terminal

from HLR, and HLR can also report the location and status of M2M Terminal

to M2M management platform in realtime.

Benefits

For carriers

M2M management platform monitor the location and status of M2M Terminals in real time, and ensure the M2M terminals are working well in the specified areas.

For subscribers

Real-time monitoring of the status and security of the M2M terminal.

Description

When the registration status of M2M terminal changed, HLR report the new

status to M2M management platform immediately in any of the following

cases:

The SGSN number on which M2M terminal is attached is changed.

The M2M terminal is detached from SGSN.

The M2M terminal is not allowed roaming in current areas.

M2M management platform query the location and status from HLR, then

HLR send MAP-PROVIDE-SUBSCRIBER-INFO to MSC to get the status

and location information.

Enhancement

None

Dependency




Page 171 of 191

The HLR implements this feature in compliance with standard protocols. The

implementation of this feature requires the cooperation of the M2M

management platform.

2.2.10.2 WHFD-220002 M2M SIM Card Theft Protection

Availability


Specification

None

Summary

This service only allows that the M2M SIM card is used on specific M2M

terminal. If M2M SIM card is used on an illegal terminal, HLR will refuse

any activity of this SIM card.

Benefits

For carriers

M2M management platform monitor the validity of terminal M2M SIM card using, prevent M2M SIM card from theft and illegal usage.

For subscribers

Real-time monitoring of the status and security of the M2M terminal.

Description

HLR check the IMEI validity of terminal M2M SIM card using. If the IMEI is

deferent from the preset IMEI, HLR will refuse any activity of this SIM card

and report a alarm to M2M management platform.

Enhancement

None

Dependency

The HLR implements this feature in compliance with standard protocols. The

implementation of this feature requires the cooperation of the M2M

management platform.




Page 172 of 191

2.3 Features of the LTE

2.3.1 WHFD-410102 Wildcard APN

Availability


Specification

3GPP 23401

3GPP 29272.

Summary

The SAE-HSS supports the wildcard Access Point Name (APN).

Benefits

For carriers

The wildcard APN function can be used to implement APN resolution. It

allows the subscriber to be identified by the PDN-GW and the intended

PDP context activation to be blocked.

For subscribers

This function simplifies the configuration on the UE. Only a wildcard (*),

rather than a specific APN, needs to be configured.

Description

During service provisioning, a wildcard (*) rather than an actual APN is

provided for a subscriber. When the UE attempts to access the MME, the

predefined APN is used for connection.

Enhancement

None

Dependency

The SAE-HSS implements this function independently. There are no special

requirements for other NEs.

2.3.2 WHFD-410103 IMSI Replacing

Availability




Page 173 of 191


Specification

None

Summary

The old SIM can work well until the new SIM card is active (means using)

after one person reissuing his SIM card. When the new SIM card is active ,

the old SIM card will be deleted in database.

Benefits

For carriers

The old SIM can work well until the new SIM card is active (means

using) .

For subscribers

None.

Description

The old SIM can work well until the new SIM card is active (means using)

after one person reissuing his SIM card. When the new SIM card is active ,

the old SIM card will be deleted in database.

Enhancement

None

Dependency



2.3.3 WHFD-410104 Inter-working with HLR

Availability


Specification

3GPP 29002

3GPP 29272.

Summary




Page 174 of 191

HSS Inter-work with HLR/AuC, and process the Mobility between E-UTRAN

and 2G/3G Accesses.

Benefits

For carriers

No need to re-provision to HSS USIM authentication information

already existing in HLR/AuC.

No need to upgrade the HLR for Mobility between E-UTRAN and

2G/3G Accesses.

For subscribers

None.

Description

HSS can retrieve authentication vectors from HLR/AUC by means of sending

MAP-SEND-AUTHENTICATION-INFO operation to HLR. If HLR does

not support the calculation of LTE authentication vectors, HLR will convert

those vectors to LTE authentication vectors.

When UE attaches to E-UTRAN, HSS send

MAP-UPDATE-GPRS-LOCATION and MAP-PURGE-MS operations to

HLR. The HLR check whether the user was previously attached on a SGSN,

and in that case HLR sends a MAP-CANCEL-LOCATION to the

corresponding SGSN and Purge the UE.

Enhancement

None




Page 175 of 191

Dependency

The HSS9860 implements this feature in compliance with standard protocols.

The implementation of this feature requires the cooperation of the HLR.

2.3.4 WHFD-410200 Roaming-Specific Functions

2.3.4.1 WHFD-410201 Roaming Area Restriction

Availability


Specification

3GPP 23401

3GPP 23402

3GPP 29272

3GPP 29273.

Summary

The HSS supports the restriction on roaming areas. The Evolved Packet

System (EPS) Regional Roaming Restriction service allows carriers to restrict

the roaming of subscribers based on the setting of regional roaming templates.

Benefits

For carriers

Carriers can restrict subscribers' roaming areas without adding any

equipment on the network. This capability helps carriers manage

subscriber mobility flexibly and effectively.

For subscribers

This service allows subscribers to choose areas where they can or cannot

roam.

Description

Zone codes identify the areas planned for implementing the EPS Regional

Roaming Restriction service. A maximum of 10 zone codes can be defined in

a regional roaming template. The zone codes are planned by carriers.

The HSS sends the subscriber's zone code list to the MME serving the

subscriber. Then the MME acts based on the contents of the zone code list. If

the zone code list does not contain the zone code mapping to the destination




Page 176 of 191

area of the subscriber, the MME prohibits the subscriber from roaming in that

area.

Enhancement

HSS9860 V900R008C20 enhancement:

When a subscriber provided with the dynamic Regional Roaming Restriction

service accesses an LTE network for the first time, the HSS obtains the

subscriber's tracking area and its neighboring tracking areas and generates a

Regional-Subscription-Zone-Code list and sends the list to the MME serving

the subscriber. Then the MME prohibits the subscriber from roaming in a

specific area based on the contents of the Regional-Subscription-Zone-Code

list and roaming restriction strategies.

During the processing of the dynamic Regional Roaming Restriction service,

the HSS performs the following operations:

When the dynamic Regional Roaming Restriction service is provided for

an offline subscriber and the subscriber accesses the LTE network for the

first time, the HSS generates the Regional-Subscription-Zone-Code list

and sends the list to the MME.

When the dynamic Regional Roaming Restriction service is provided for

an online subscriber and the subscriber wants to change the allowed

roaming areas, the HSS deletes the old Regional-Subscription-Zone-Code

list upon receiving a RESET BINDEDTAI command and generates a new

Regional-Subscription-Zone-Code list when the subscriber accesses an

LTE network again.

When the dynamic Regional Roaming Restriction service is withdrawn

from an online subscriber, the HSS sends an Insert Subscriber Data

message to the MME. Next time when the subscriber attempts to access an

LTE network, the MME sends a Notify Request message to the HSS. The

HSS sends an Insert Subscriber Data message containing the

newly-generated Regional-Subscription-Zone-Code list to the MME.

Figure Dynamic Regional Roaming Restriction service flow for an offline

subscriber that accesses an LTE network for the first time




Page 177 of 191

1. A UE sends an Initial Attach Request message to the MME.

2. The MME authenticates the UE.

3. If the authentication succeeds, the MME sends an Update Location

message to the HSS.

4. The HSS determines that the UE accesses the LTE network for the first

time and sends an Update Location ACK message to the MME.

5. The MME sends an Initial Attach ACK message to the UE.

6. The HSS obtains the subscriber's tracking area and its neighboring tracking

areas and saves a tracking area list and a mapping list between the tracking

area and the zone code. Besides, the HSS incorporates these two lists into

a Regional-Subscription-Zone-Code list and contains the list in an Insert

Subscriber Data message sent to the MME.

7. The MME sends an Insert Subscriber Data ACK message to the HSS.

Dependency


The implementation of this feature requires the cooperation of the MME.

2.3.4.2 WHFD-410202 Local Breakout

Availability





Page 178 of 191

Specification

3GPP 23401

3GPP 23402

3GPP 29272

3GPP 29273.

Summary

The SAE-HSS supports the Local Breakout function.

Benefits

For carriers

This function allows carriers to provide IP services for the subscribers in

the visited PLMN (VPLMN) by using the PDN-GW on the VPLMN. It

helps to enhance the competitive edge of carriers.

For subscribers

This function enables subscribers to enjoy the IP services provided in the

VPLMN.

Description

Local breakout is a roaming mode that is different from the home routed

mode.

In the case of home routed mode, the PDN-GW in the home network provides

IP services for the subscribers roaming to a VPLMN.

The local breakout function allows the PDN-GW on the VPLMN to provide

IP services for roaming subscribers.Figure 1-5 shows the local breakout

procedure.




Page 179 of 191

Figure 1-5 Local breakout procedure

Enhancement

None

Dependency



2.3.4.3 WHFD-410203 Diameter Node-Specific Roaming Restriction

Service

Availability


Specification

3GPP 23401

3GPP 23402

3GPP 29272

3GPP 29273.

Summary

The Diameter Node-Specific Roaming Restriction service allows carriers to

manage the mobility of subscribers by configuring diameter node-covered

service areas in which subscribers can roam. A diameter node can be the

Mobile Management Entity (MME), Authentication, Authorization, and

Accounting (AAA) server, or S4-Serving GPRS Support Node (S4-SGSN).




Page 180 of 191

The allowed or restricted roaming area can be a city or a region

Benefits

For carriers

Carriers can allow or restrict subscriber roaming in the areas covered by

the MME, S4-SGSN, or AAA server without adding any devices on the

network. The ability to configure diameter node-covered roaming areas

helps carriers to manage subscriber mobility flexibly and effectively.

For subscribers

Subscribers can subscribe to the allowed or restricted roaming areas at

will.

Description

The Diameter Node-Specific Roaming Restriction service is implemented

based on diameter node templates configured with roaming restriction rules.

The roaming scope of a subscriber is determined by the diameter

node-specific roaming restriction template to which the subscriber subscribes.

The host name or domain name of a single or multiple Diameter nodes can be

defined, or blacklisted and whitelisted Diameter nodes can be configured in

the template.

In an S6a location update or an S6d location update, the HSS or the HLR

determines whether to allow a subscriber to roam in the area covered by the

MME or S4-SGSN based on the Diameter node-specific roaming restriction

template to which the subscriber subscribes. If the subscriber is not allowed to

roam in the specified area, the HSS or the HLR rejects the location update. If

the subscriber is allowed to roam in the area, the HSS or the HLR continues

processing the location update.

In an SWx authentication procedure, the HSS or the HLR determines whether

to allow a subscriber to roam in the area covered by the AAA server based on

the Diameter node-specific roaming restriction template to which the

subscriber subscribes. If the subscriber is not allowed to roam in the specified

area, the HSS or the HLR rejects the authentication request. If the subscriber

is allowed to roam in the area, the HSS or the HLR continues processing the

authentication request.

Roaming restricted

shows a failed location update during which a subscriber's roaming is

restricted.




Page 181 of 191

Figure 1

1. The MME or S4-SGSN sends an Update Location REQ message to the

HSS.

2. The HSS detects that the subscriber cannot roam in the area covered by the

MME or S4-SGSN based on the IMSI and host name or domain name of

the MME or S4-SGSN carried in the Update Location REQ message and

sends an Update Location ERR message indicating a location update

failure to the MME or S4-SGSN.

Roaming allowed

NOTE:

Assume that a subscriber has passed the HLR-specific roaming restriction

check, Customized Applications for Mobile Enhanced Logic (CAMEL)

roaming restriction check, and operator determined barring (ODB)-ROAM

check.

shows a successful location update during which a subscriber's roaming is

allowed.

Figure 2




Page 182 of 191

1. The MME or S4-SGSN sends an Update Location REQ message to the

HSS.

2. The HSS detects that the subscriber is allowed to roam in the area covered

by the MME or S4-SGSN based on the IMSI and host name or domain

name of the MME or S4-SGSN carried in the Update Location REQ

message and sends an Update Location RSP message indicating a

successful location update to the MME or S4-SGSN.

Enhancement

None

Dependency

None.

2.3.4.4 WHFD-410204 Multi-HPLMN Function

Availability


Specification

3GPP 23401

3GPP 23402

3GPP 29272

3GPP 29273.

Summary

This function is applicable only when multiple HPLMNs are used.

Benefits

For carriers

This function allows carriers to provide multiple PLMN id in the home

PLMN (HPLMN). It helps to enhance the competitive edge of carriers.

For subscribers

None.

Description

allows carriers to provide multiple PLMN id in the home PLMN (HPLMN)

Enhancement




Page 183 of 191

None

Dependency



2.3.4.5 WHFD-410205 PLMN-Specific Roaming Restriction Service

Availability


Specification

3GPP 23401

3GPP 23402

3GPP 29272

3GPP 29273.

Summary

The PLMN-Specific Roaming Restriction service allows carriers to manage

the mobility of subscribers by configuring Public Land Mobile Networks

(PLMNs) in which the subscribers can roam.

The allowed or restricted PLMNs are signed roaming agreements with the

local PLMN.

Benefits

For carriers

Carriers can allow or restrict subscriber roaming in PLMNs without

adding any devices on the network. The ability to configure PLMN

access for roaming subscribers helps carriers to manage subscriber

mobility flexibly and effectively.

For subscribers

Subscribers can subscribe to the allowed or restricted roaming areas at

will.

Description

The PLMN-Specific Roaming Restriction service is implemented based on

PLMN templates configured with roaming restriction rules. The roaming

scope of a subscriber is determined by the PLMN-specific roaming restriction

template to which the subscriber subscribes. In the template, a PLMN or




Page 184 of 191

multiple PLMNs can be defined, or blacklisted and whitelisted PLMNs can be

configured.

In an S6a location update or an S6d location update, the HSS/HLR determines

whether to allow a subscriber to access the requested PLMN based on the

PLMN-specific roaming restriction template to which the subscriber

subscribes. If the requested PLMN is blacklisted, the HSS/HLR rejects the

location update request. If the requested PLMN is not blacklisted, the

HSS/HLR continues processing the location update.

In an SWx authentication procedure, the HSS/HLR determines whether to

allow a subscriber to access the requested PLMN based on the PLMN-specific

roaming restriction template to which the subscriber subscribes. If the

requested PLMN is blacklisted, the HSS/HLR rejects the authentication

request. If the requested PLMN is not blacklisted, the HSS/HLR continues

processing the authentication request.

Enhancement

None

Dependency


The implementation of this feature requires the cooperation of the MME,

AAA server and S4-SGSN.

2.3.5 WHFD-410106 Auto-Provisioning for LTE

Availability


Specification

3GPP TS 29.272, 29.002

Summary

The Auto Provision of LTE Service allows carriers to provide long term

evolution (LTE) services for a subscriber that has not been defined in the HSS

without changing its USIM cards and MSISDN numbers.

Benefits

For carriers

Carriers can provide LTE services for a subscriber that has not been

defined in the HSS without changing its MSISDN number and USIM

card.




Page 185 of 191

Eliminate the need to purchase LTE licenses and reduce investment.

For subscribers

Subscribers can use LTE services without subscription.

Description

HSS and HLR is deployed separately：

When UE attach to the LTE network for the first time, the HSS obtain the

GPRS subscription data from the HLR and converts it to LTE subscription

data.

HSS and HLR are combined：

When UE attach to the LTE network or GPRS subscription is changed, the

HSS converts the GPRS subscription data to LTE subscription data and sent to

MME.

MSC

2G/3G

SGSN

LTE

HLR

MME

BSS

SAE-HSS

User A:

2G/3G data

User A:Mapping

2G/3G GPRS data

into EPS data

Gr S6a

Gr’

C/D

CS/PS data EPS data

MSC

2G/3G

SGSN

LTE

MME

BSS

SAE-HSS

User B:

2G/3G data, no

EPS data

GrS6aC/D

CS/PS/EPS data




Page 186 of 191

Enhancement

None

Dependency

The HSS implements this function independently. There are no special


2.3.6 WHFD-410300 Supporting of VoLTE

2.3.6.1 WHFD-410301 Supporting of CS Fallback

Availability


Specification

3GPP 23272

3GPP 23401

3GPP 29272.

Summary

The Circuit Switched Fallback in Evolved Packet System (CS Fallback)

feature enables carriers to reuse the circuit switched (CS) infrastructure to:

Provide voice services for the subscribers who are attached to both the

evolved packet system (EPS) and the CS domain.

Provide short message service (SMS) at the initial phase of long term

evolution (LTE) deployment

Benefits

For carriers

Carriers can provide voice services and SMS service at the initial phase

of LTE deployment without building the IP multimedia subsystem (IMS).

Carriers can reuse the GSM/EDGE radio access network (GERAN) and

UMTS terrestrial radio access network (UTRAN) while shifting to the

future-proof long term evolution (LTE) network. By doing so, carriers

can maximize the return on CS investments.

For subscribers

Subscribers can use the high-speed data services of the LTE, as well as

CS Fallback voice services and SMS service by using the same terminal.

Description




Page 187 of 191

The LTE network at the initial phase usually covers only hot spots and is

limited in continuous coverage. As LTE deployment progresses, tracking areas

(TAs) should be well planned to allow all the 2G/3G location areas in a TA to

be served by the same MSC server. This ensures that when the UE initiates a

combined TA/LA update, the MME always redirects the UE to the MSC

server that is serving the 2G GERAN or 3G UTRAN. If the MME selects the

wrong MSC server, roaming retry may take place. The MME is able to select

the appropriate MSC server because it derives a VLR number from the

tracking area identity (TAI) of the current cell based on the configuration data.

An MME covers multiple hot spots and maintains IP connectivity with

multiple MSC servers.

In actual usage, the Mapping relations between TA and LA may lead the

combined EPS/IMSI attach to a wrong VLR. In that case, it triggers the

Roaming Retry function.

Enhancement

None

Dependency


The implementation of this feature requires the cooperation of the MME,

GMSC and MSC/VLR.

2.3.6.2 WHFD-410302 Supporting of SRVCC

Availability


Specification

3GPP 23216

3GPP 23401

3GPP 29272

Summary

The Single Radio Voice Call Continuity (SRVCC) feature allows subscribers

to continue an ongoing call when roaming from an evolved universal

terrestrial radio access network (E-UTRAN) to a UMTS terrestrial radio

access network (UTRAN) or GSM/EDGE radio access network (GERAN).

This is achieved by using the handover function of user equipment (UE) and

network equipment.

The enhanced SRVCC (eSRVCC) feature is introduced to shorten the duration

of voice interruption caused by SRVCC handover. In the eSRVCC network

architecture, the access transfer control function (ATCF)/access transfer

gateway (ATGW) is added between the proxy-call session control function

(P-CSCF) and the interrogating-CSCF (I-CSCF)/serving-CSCF (S-CSCF). If




Page 188 of 191

an SRVCC handover might occur in a call, the media session is anchored to

the ATGW. When an SRVCC handover does occur, only media information on

the ATGW needs to be updated. Media information on the UE does not need

to be updated.

Benefits

For carriers

Carriers can provide voice services and SMS service at the initial phase

of LTE deployment without building the IP multimedia subsystem (IMS).

Carriers can reuse the GSM/EDGE radio access network (GERAN) and

UMTS terrestrial radio access network (UTRAN) while shifting to the

future-proof long term evolution (LTE) network. By doing so, carriers

can maximize the return on CS investments.

For subscribers

Subscribers can use the high-speed data services of the LTE, as well as

CS Fallback voice services and SMS service by using the same terminal.

Description

Logical architecture of the eSRVCC feature

The general procedure for an eSRVCC handover is as follows:

1. When LTE co-exists with GSM or UMTS, E-UTRAN decides to initiate an eSRVCC

handover to GERAN or UTRAN based on the measurement reports sent from a UE.

If an eSRVCC handover is required, E-UTRAN sends a handover request to the

MME.

2. When the MME receives the handover request, it splits voice bearers from

non-voice bearers based on QoS Class Identifier (QCI) 1 associated with voice

bearers and the SRVCC handover (HO) indication in the message. Meanwhile, the




Page 189 of 191

MME selects an SRVCC IWF based on the Target ID indicated in the message and

initiates the PS-CS voice handover procedure towards the selected SRVCC IWF.

3. When the SRVCC IWF receives the handover request message, it identifies the

target MSC by the Target ID indicated in the message. Then, the SRVCC IWF

initiates a handover procedure towards the target MSC to redirect the UE from

E-UTRAN to GERAN or UTRAN. It also routes the UE's call to IMS.

Enhancement

None

Dependency


The implementation of this feature requires the cooperation of the MME, SCC

AS.

2.3.6.3 WHFD-410303 Optimized Routing Based on Selective

Anchoring

Availability


Specification

3GPP 23228

3GPP 29272

3GPP 29328

3GPP 29329

3GPP 29002

Summary

HSS anchor voice calls to IMS domain based on the subscription and

IMS-domain register status.

Benefits

For carriers

Carriers can anchor calls to IMS to provide diversified services for LTE

subscribers. This helps carriers improve subscriber satisfaction and

expand their IMS subscriber base.

HSS anchor calls to IMS based on the subscription and IMS-domain

register status, avoid to anchor all subscribers’ call to IMS and save the

network resource.




Page 190 of 191

For subscribers

S VoLTE subscribers can use diversified IMS services even when they

are in the CS domain.

Description

After the HSS receives a Send Routing Information (SRI) message, the

HSS checks whether MT anchoring is required. If the called VoLTE

subscriber has the convergent services and registered in IMS domain, the

HSS considers that MT anchoring is required. The HSS sends an

extension PRN message to the Anchor AS, requesting that the Anchor AS

allocate an IMRN. After the HSS obtains the IMRN from the Anchor AS, the

HSS sends the IMRN to the gateway MSC (GMSC) server. Based on the

IMRN, the GMSC server routes the call to IMS.

Enhancement

None

Dependency

The HSS9860 implements this feature in a extended protocols. The

implementation of this feature requires the cooperation of the GMSC.MGCF,

IMS-HSS, AS.

2.3.6.4 WHFD-410304 IP SMS Interworking

Availability


Specification

3GPP TS 23.040

3GPP TS 29.002

3GPP TS 23.204

3GPP TS 24.247

3GPP TS 24.341

Summary

The IP SMS Interworking service enables short message delivery between IP

multimedia subsystem (IMS) domains and circuit switched (CS) domains.

Benefits

For carriers




Page 191 of 191

Carriers can continue to provide the traditional SMS service when

migrating their CS networks towards LTE networks. This increases their

return on investment (ROI) and improves their competitive edge.

For subscribers

Subscribers can choose either IMS or CS domains to send and receive

short messages.

Description

Voice over LTE (VoLTE) is an IMS-based voice solution defined by 3rd

Generation Partnership Project (3GPP). The IP-SM-GW in the VoLTE

solution enables IP-based LTE terminals to exchange short messages with

CS terminals. The SMSC stores and forwards short messages. The SMSC

also generates and sends delivery reports.

The Short Message Service (SMS), which is a basic CS teleservice, allows

subscribers to send and receive text messages through a short message

service center (SMSC). IMS domains support IP short messages, while CS

domains support CS short messages. When an LTE terminal in an IMS

domain attempts to send an IP short message to a CS terminal, the

IP-SM-GW converts the IP short message into a CS short message and

sends it to the SMSC. If the CS terminal is powered on, the SMSC forwards

the CS short message to the CS terminal. If the CS terminal is powered off,

the SMSC stores the CS short message until the CS terminal is powered

on or the maximum storage time is reached.

Enhancement

None

Dependency


The implementation of this feature requires the cooperation of the S-CSCF,

SMSC.

Documents

Huawei SingleSDB V100R006C00 HSS9860 Feature Description(HLR and EPC-HSS FE Part)