Railway Operational Communication Solution GSM-R HLR9820 Product Description1.0 (20090512)

GSM-R HLR9820 Product Description
Issue
1.0
Date
2013-02-25
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Contents
1 Product Orientation ............................................................................................................ 4
1.1 Huawei USC Solution .......................................................................................................................... 4
1.2 Product Orientation of the HLR9820 ................................................................................................... 6
1.3 Major Functions of the HLR9820 ........................................................................................................ 8
1.4 Key Benefits ......................................................................................................................................... 9
2 Overview of the HLR9820 ............................................................................................... 11

2.1 Physical Structure............................................................................................................................... 11
2.2 Logical Structure ................................................................................................................................ 16
3 System Features ................................................................................................................. 21

3.1 Distributed Structure .......................................................................................................................... 21
3.2 ATCA-Compatible OSTA 2.0 Hardware Platform ............................................................................. 22
3.3 Memory Data Management Technology ............................................................................................ 23
3.4 Multi-Level Data Backup Mechanism ............................................................................................... 23
3.5 Virtual HLR Function......................................................................................................................... 24
3.6 Large Capacity and High Integrity ..................................................................................................... 25
3.7 Separate Data Processing and Service Processing ............................................................................. 25
3.8 Physical Self-Redundancy Solutions ................................................................................................. 26
3.9 Smooth Data Convergence ................................................................................................................. 27
3.10 Standard and Open Data Access Interface........................................................................................ 27
3.11 Comprehensive Data Statistics and Analysis .................................................................................... 28
4 Technical Specifications .................................................................................................. 29

4.1 Performance Specifications ................................................................................................................ 29
4.2 Reliability Specifications ................................................................................................................... 30
4.3 Cabinet Specifications ........................................................................................................................ 30
4.4 Power Consumption ........................................................................................................................... 31
4.5 Clock Specifications........................................................................................................................... 32
4.6 EMC Specifications ........................................................................................................................... 34
4.7 Environment Requirements ................................................................................................................ 34
5 Acronyms and Abbreviations ......................................................................................... 42

Huawei Proprietary and Confidential
Issue 1.0 (2013-02-25)
Page 3 of 45
Copyright Huawei Technologies Co., Ltd.
Product Orientation
1.1 Huawei USC Solution

At present, the service data of subscribers is distributed in different functional entities
in the network, and the functional entities have different data management modes.
Isolated information "islands" thus emerge. The isolated information "islands" lack
scalability, making the carriers' networks very complicated. In addition, it is hard for
carriers to make use of the isolated information to develop value-added services. As a
result, carriers are facing more challenges in providing the same service experience to
subscribers over multiple types of networks.
Nowadays, more and more carriers come to realize the importance of convergence and
centralized management of the subscriber service data, and put forward various
solutions. To realize the subscriber-oriented convergence of subscriber service data
becomes a development trend in the telecommunication industry.
Huawei Unified Subscriber Center (USC) incorporates the functions of the network
entities such as the HLR, HSS, AAA, MNP, EIR, and GUP. It can converge the
subscriber service data required by the NEs in the public land mobile network (PLMN),
public switched telephone network (PSTN), broadband network, and multimedia
network.
The USC can realize centralized management of the subscriber service data and
provide an open data interface. It can simplify network deployment, accelerate the
provisioning of new services, and prompt service innovation. The USC solution helps
carriers to provide competitive integrated services.
Figure 1-1 illustrates Huawei USC solution.

Issue 1.0 (2013-02-25)
Page 4 of 45
Figure 1-1 Huawei USC solution
AAA: Authentication, Authorization

and Accounting
CRBT: Color Ring Back Tone
HLR: Home Location Register
MGCF: Media Gateway Control
Function
SGSN: Serving GPRS Support Node
AS: Application Server
BE: Back End
CSCF: Call Session

Control Function
HSS: Home Subscriber
Server
MSC: Mobile Switching
Center
FE: Front End

IMS: IP Multimedia Subsystem
MNP: Mobile Number Portability
Huawei USC consists of the Back End (BE) and the Front End (FE).
BE
The BE is subscriber-oriented and uses the directory service to store the
subscriber data. It allows the subscriber data to be added, deleted, queried, and
updated through the directory service. It also provides the data required by the
FE.
FE
The FE processes signaling access services.
The FE does not store subscriber data. It obtains data services from the BE
through directory services.
Huawei USC solution provides the HLR-FE, HSS-FE, AAA-FE, MNP-FE, and
AS-FE.
The implementation of Huawei USC solution comprises three phases:

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

Phase I: network simplification

The USC is deployed as the HLR, HSS, or AAA. It features large capacity and
provides high network security. The USC solution can reduce the number of NEs
used in the network and simplify network deployment.
Phase II: data convergence

The USC converges the subscriber data relating to voice services, multimedia
services, and broadband services. It supports data platform standardization, data
sharing, and service convergence.
Phase III: service innovation

The convergence of subscriber data provides a unified data source, which makes
rapid service innovation and efficient data operation and management possible.
Based on the unified data source and centralized data management, carriers can
provide more value-added services to attract more subscribers and to enhance the
competitive strength.
1.2 Product Orientation of the HLR9820

The HLR9820 is the product provided by Huawei USC solution in the first phase.
Figure 1-2 illustrates the evolution of the HLR9820 towards the USC.
Figure 1-2 Evolution of the HLR9820 towards the USC
AAA: Authentication, Authorization

and Accounting
CRBT: Color Ring Back Tone
GMLC: Gateway Mobile Location
Center
IMS: IP Multimedia Subsystem
AS: Application Server
BE: Back End
CSCF: Call Session Control Function

FE: Front End

HSS: Home Subscriber Server
MGCF: Media Gateway Control Function
MSC: Mobile Switching Center

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

MNP: Mobile Number Portability
SMC: Short Message Center
SCP: Service Control Point
The HLR9820 provides the functions of the HLR. It is shared by the circuit switched
(CS) domain and the packet switched (PS) domain in the GSM or the UMTS network.
The HLR9820 compared with the traditional HLR, the HLR9820 consists of:
HLR-BE
The HLR-BE stores subscriber data. It provides services such as data addition,
data deletion, data update, and date query to the HLR-FE.
HLR-FE
The HLR-FE is connected with the signaling network. It processes IP signaling,
ATM 2Mbit/s signaling, and TDM signaling. The HLR-FE supports the same
protocols and interfaces as the HLR.
The HLR-FE does not store subscriber data. It obtains data services from the
HLR-BE.
Figure 1-3 shows the difference between the HLR9820 and the traditional HLR.
Figure 1-3 Difference between the HLR9820 and the traditional HLR
Service layer
SCP
Service layer
SMC
GMLC
SCP
Signaling network
SMC
GMLC
Signaling network
HLR
HLR9820
HLR-FE
HLR-BE
Signaling network
Signaling network
Control layer
SGSN
Control layer
MSC server
SGSN
MSC server

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

BE: Back End
SCP: Service Control Point
FE: Front End

HSS: Home Subscriber Server
GMLC: Gateway Mobile Location Center

MSC: Mobile Switching Center
SMC: Short Message Center
1.3 Major Functions of the HLR9820

The HLR9820 provides the following functions:
Subscriber Data Management
Mobility Management
Support of the Call-Related Processing
Support of the ATI
Functions of the AuC
Subscriber Data Management

The HLR9820 manages the following data:
Basic subscriber data

The HLR9820 stores and manages the basic data of the subscribers defined in it.
The basic data stored in the HLR9820 includes the information on:
Subscriber identification
Basic services provided to subscribers
Supplementary services provided to subscribers
Operator-determined barring (ODB) services provided to subscribers
Roaming restriction
CAMEL services provided to subscribers
GPRS services provided to subscribers
Authentication data
Upon the request of the visitor location register (VLR) or serving GPRS support
node (SGSN), the HLR9820 provides the authentication data to the VLR or
SGSN. The HLR9820 can send one to five authentication triplets or quintuplets at
a time.
In addition, the HLR9820 can convert the UMTS quintuplets into GSM triplets.
Mobility Management
The HLR9820 supports the mobility management of mobile subscribers in the CS
domain and the PS domain.
Mobility management in the CS domain

The HLR9820 supports the mobility management of mobile subscribers over the
Mobile Application Part (MAP) interface in the CS domain.
The mobile management comprises:
Location update
Issue 1.0 (2013-02-25)
Page 8 of 45
Location cancellation
Mobility management in the PS domain

The HLR9820 supports the mobility management of mobile subscribers over the
MAP interface in the PS domain.
The mobile management comprises:
GPRS routing area update
GPRS routing area cancellation
Support of the Call-Related Processing

The HLR9820 responds to the Sending Routing Information (SRI) request sent from
the MSC and provides a mobile station roaming number (MSRN) in a
mobile-terminated call (MTC).
Support of the ATI

The HLR9820 supports the any time interrogation (ATI) initiated by the service
control point (SCP). Through the ATI, the SCP and HLR9820 obtain the location and
status of the mobile stations (MSs).
Functions of the AuC

The authentication center (AuC) processes the security data for subscriber
authentication.
Upon the request of the VLR or SGSN, the AuC generates an authentication quintuplet
or triplet, and sends the authentication quintuplet or triplet to the VLR or SGSN
through the HLR9820. The AuC then verifies the international mobile subscriber
identity (IMSI) of the subscriber to ensure the validity of the subscriber.
1.4 Key Benefits

The HLR9820 features high reliability, large capacity, and high integration, and
provides the capability of data convergence. It can help carriers to provide tailored
services and gain competition predominance.
Highly Reliable Network and Enhanced QoS

The HLR9820 adopts totally new design and highly efficient mechanisms to ensure
high network reliability and protect the interest and brand image of carriers.
The high reliability and QoS are attributed to the following features of the HLR9820:
Fully-distributed structure
ATCA-compatible OSTA 2.0 hardware platform
Memory data management mechanism
Multi-level data backup mechanism

Issue 1.0 (2013-02-25)
Page 9 of 45
Implementing Centralized Network Deployment and Slashing the OPEX

The HLR9820 features large capacity and high integration. The standard configuration
of six cabinets can support 100 million subscribers.
The HLR9820 provides the virtual HLR function, which allows authority-based and
domain-based management of the large-capacity HLR. This feature can help carriers to
realize centralized network deployment.
The centralized deployment of the large-capacity HLR can greatly cut down the
operation expenditure (OPEX). It helps carriers to:
Reduce the number of NEs used in the network and simplify network
deployment.
Reduce the equipment maintenance cost and maintenance personnel cost.
Save power consumption and reduce the property leasing expense.
Laying the Foundation for Service Convergence

To offer subscribers with seamless communication experience over multiple types of
networks, carriers must provide subscriber-oriented network-across services. The
service convergence, however, is implemented based on data convergence. The
HLR9820 provides the ability to converge the subscriber data of various types of
services. It also provides standard and open interfaces. All these features lay the
foundation for service convergence.

Issue 1.0 (2013-02-25)
Page 10 of 45
Overview of the HLR9820
2.1 Physical Structure

This section describes the physical structure of the HLR9820. It consists of:
Product Appearance
Cabinet Configuration
2.1.1 Product Appearance

This section describes the hardware composition of the HLR9820. It consists of:
Cabinet
OSTA 2.0 Subrack
Cabinet
The HLR9820 uses Huawei N68E-22 cabinets. Figure 2-1 shows an N68E-22 cabinet.

Issue 1.0 (2013-02-25)
Page 11 of 45
Figure 2-1 HLR9820 cabinet
The N68E-22 cabinet is a standard 19" cabinet and complies with the following
international standards:
IEC60297-1, Dimensions of mechanical structures of the 482.6 mm (19 in) series

Part 1:Panels and racks

Part 2:Cabinets and pitches of rack structures

Part 3:Subracks and associated plug-in units
For the technical specifications of the N68E-22 cabinet, refer to section 4.3 "Cabinet
Specifications."
OSTA 2.0 Subrack

The HLR9820 adopts the ATCA-compatible OSTA 2.0 hardware platform. Figure 2-2
shows the OSTA 2.0 subrack.

Issue 1.0 (2013-02-25)
Page 12 of 45
Figure 2-2 OSTA 2.0 subrack
The OSTA 2.0 subrack has the following features:

The subrack is 14 U high and 19" wide. It can be installed in any standard 19"
cabinet.
The subrack provides 14 front slots for the USPs and 14 back slots for the USIs.
The subrack is configured with a dual-star high-speed backplane. The backplane

provides the redundancy of the following buses:
Dual-star intelligent platform management bus (IPMB)
Service data bus
Power bus
Clock bus
The boards and modules are interconnected through the buses provided by the
backplane. Thus, the number of cables used between boards and modules is
greatly reduced.
The subrack can be configured with a maximum of four power modules, which
supply power to the components in the subrack through the backplane. The power
modules can work in 2+2 or 2+1 redundancy mode.
The subrack has one fan box that holds 12 fans. The fan box implements the heat
dissipation of the subrack.
The subrack provides rear cabling troughs. This customary design makes the
subrack maintenance convenient.
The subrack has passed the EMC and UL certifications.
The subrack supports the Network Equipment Building Specification (NEBS).

Issue 1.0 (2013-02-25)
Page 13 of 45
2.1.2 Cabinet Configuration

Depending on the components installed in the cabinet, the HLR9820 cabinets can be
classified into:
Integrated cabinet
Extended cabinet
The components to be installed in the cabinets depend on the system capacity.
The components that can be installed in the integrated cabinet include the following:
Power distribution box (PDB)
SAU subrack
Air deflector
OSTA 2.0 subrack
KVMS
LAN switches
Disk array
Figure 2-3 shows the typical configuration of the integrated cabinet.

Issue 1.0 (2013-02-25)
Page 14 of 45
Figure 2-3 Typical configuration of integrated cabinet
PDB (3U)
Filler panel (1U)
OSTA 1.0 subrack (9U)
Air deflector (2U)
Filler panel (1U)

KVM(1U)
Filler panel (1U)
LAN switch-3 (1U)
Cabling trough (1U)
LAN switch-2 (1U)
Cabling trough (1U)
LAN switch-1 (1U)
Cabling trough (1U)
LAN switch-0 (1U)
Cabling trough (1U)
Filler panel (2U)
Disk array (3U)
Filler panel (1U)
Integrated cabinet
The components that can be installed in the extended cabinet include the following:
PDB
SAU subracks
Air deflector
OSTA 2.0 subrack
Figure 2-4 shows the typical configuration of the extended cabinet.

Issue 1.0 (2013-02-25)
Page 15 of 45
Figure 2-4 Typical configuration of extended cabinets
PDB (3U)
PDB (3U)
Filler panel (1U)
Filler panel (1U)
Air deflector (2U)
Air deflector (2U)
Filler panel (2U)

Filler panel (3U)

Air deflector (2U)
Filler panel (2U)
Filler panel (1U)
Filler panel (1U)
Extended cabinet 1
Extended cabinet 2
2.2 Logical Structure

The HLR9820 consists of the following functional layers:
Signaling Processing Layer
Subscriber Data Management Layer
Data Service Layer

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

Data Storage Layer
O&M Layer
Figure 2-5 shows the logical structure of the HLR9820.

Figure 2-5 Logical structure of the HLR9820
Signaling
Network
Signaling Processing
HLR-FE
O&M
SAU
BAM
Service Processing
NMS
SCF
Data Service
DRU
Cluster 1
DRU
Cluster 2
Subscriber data
management
SMU
DSU
Cluster 1
DSU
Cluster 2
DSU
Cluster 3
SMF
Provision
System
Data storage
DBMS
HLR-BE
BAM: Back Administration Module
DBMS: Database Management System
FE: Front End
SMF: Subscriber Management Function
HLR9820
BE: Back End
DRU: Data Routing Unit
SAU: Signaling Access Unit
SMU: Subscriber Management Unit
DSU: Data Service Unit

SCF: Service Control Function
NMS: network management system

Issue 1.0 (2013-02-25)
Page 17 of 45
2.2.1 Signaling Processing Layer

The signaling processing layer leads in and processes signaling messages. It consists
of:
SAU
SCF
SAU
The signaling access unit (SAU) performs the following functions:
Receiving the signaling messages sent from other NEs
Processing the received signaling messages to the TCAP layer
Sending the processed messages to the SCF for processing
SCF
The service control function (SCF) processes MAP service logics. It performs the
following functions:
Processing the MAP messages, such as the SRI request and location update
request, sent from the SAU
Processing the MAP message for inserting subscriber data initiated by the SMF
because of the operations such as updating subscriber data and simulated sending
the Cancel Location message
Interacting with the DRU to obtain the desired subscriber data from the DSU or
to update the subscriber data stored in the DSU
Implementing the authentication-related operations
2.2.2 Subscriber Data Management Layer

The subscriber data management layer manages the subscriber data and implements
the configuration of the global data. It consists of:
SMU
SMF
SMU
The subscriber management unit (SMU) performs the following functions:
Providing interfaces to business halls to lead in the provision system
Interpreting the human-machine language (MML) commands sent from the

provision system or the SMU client, and sending the commands to the SMF for
processing
SMF
The subscriber management function (SMF) processes the messages sent from the
SMU. It performs the following functions:
Issue 1.0 (2013-02-25)
Page 18 of 45

Receiving the messages for the operations such as subscriber definition,

subscriber deletion, and subscriber data update from the SMU, verifying
parameters according to the related interface specifications, and checking service
conflict according to the related protocols
Initiating the MAP message for inserting subscriber data and sending the message
to the SCF during the operations such as updating subscriber data and simulated
sending of the Cancel Location message
Interacting with the DRU to query the subscriber data, global data, or template
data from the DSU or to modify the subscriber data, global data, or template data
in the DSU based on the MML command received from the SMU server
2.2.3 Data Service Layer

The data service layer provides data services that are independent of service
applications. It supports distributed data storage, data caching in memory, and remote
redundancy of the data unit. The data service unit consists of:
DRU
DSU
DRU
The data routing unit (DRU) queries the subscriber data and provides the data routing
function.
The HLR9820 uses multiple DSU clusters to store subscriber data. A routing module is
required to locate the DSU cluster, which stores the data queried, based on the
subscriber identity, and then to choose a DSU based on the load-balancing strategy to
provide data services.
The DRU stores the mapping between the Key values (UID and IMSI or MSISDN)
and the DSU cluster ID. In addition, the DRU stores the mapping between the IMSI of
a subscriber and the UID or MSISDNor the auxiliary IMSI (if the dual-IMSI service is
provided). Therefore, the DRU can locate the DSU cluster, in which the required
subscriber data is stored, based on the Key values, and choose a DSU from the DSU
cluster to provide the data based on the load-balancing strategy.
The HLR supports multiple DRU clusters. The routing data is stored in multiple DRU
clusters. The SMF and SCF modules store the mapping between the Key values of a
subscriber and the DRU cluster ID. Therefore, they can locate the DRU cluster, in
which the required subscriber data is stored, based on the Key values.
DSU
The HLR9820 uses multiple data service unit (DSU) clusters to store subscriber data.
The DSU provides, adds, deletes, or updates data upon the request of the DRU.
The DSU clusters store subscriber data based on the capacity-balancing strategy. All
the DSUs in a DSU cluster store the same subscriber data and work in load-sharing
mode.

Issue 1.0 (2013-02-25)
Page 19 of 45
2.2.4 Data Storage Layer

The data storage layer adopts the highly reliable commercialized database
management system. It also uses the disk array to provide permanent storage of
subscriber data. The hard disks of the disk array adopt RAID technology and hot spare
disks to ensure the security of subscriber data.
2.2.5 O&M Layer

The O&M layer implements the operation and maintenance of the other functional
units.
The HLR9820 provides a graphical user interface (GUI) based on the tree structure for
the O&M terminals. The GUI is easy to use and allows efficient running of commands.
In addition, the network management system (NMS) can be flexibly built up based on
the network structure, management requirements, and investment scale. The O&M
terminals support concurrent access of multiple users from the local and remote ends.
The O&M layer performs the following functions:
Configuration management
Through the O&M terminals, users can configure the data such as the hardware
data, local site data, and signaling data.
Equipment maintenance
The O&M layer processes the maintenance commands sent from the client or
NMS. It helps the maintenance staff to identify or rectify faults.
Fault management
When a fault occurs, the O&M layer reports an alarm. Thus, the maintenance
staff can identify the fault in time.
Performance measurement
Through performance measurement, users can learn:
Operation status of the HLR9820
Signaling exchange
Utilization of user resources and system resources
The O&M layer provides reliable data for network planning, system monitoring,
and operation management. When the communication resources are insufficient,
the O&M layer can provide the detailed resource information on the equipment.
Trace management
Through the O&M terminals, users can perform interface tracing and subscriber
tracing, and view the information traced. The trace management helps the
maintenance staff to identify faults.
Provision of NM interfaces
The O&M layer provides NM interfaces. Through the NM interfaces, users can
connect the HLR9820 with the upper-level NMS to perform centralized
management and maintenance of the equipment.

Issue 1.0 (2013-02-25)
Page 20 of 45
System Features
3.1 Distributed Structure

The distributed structure allows multiple functional entities that are identical in a
system to work in load-sharing mode to accomplish a certain function. The most
distinguished feature of the distributed structure is resource sharing in the system.
When any functional entity fails, the load will be automatically switched over to other
functional entities. Thus, the service provisioning of the whole system is not adversely
affected.
Figure 3-2 illustrates the distributed structure.
Signaling network
HLR-FE
BAM
NMS
Open/Standard
interface
Data
Cluster
Data
Cluster
BAM
Data
Cluster
SMU
HLR-BE
Provision System
HLR9820
NMS: network management system
SMU: Subscriber Management Unit
BAM: Back Administration Module

FE: Front End
BE: Back End

Issue 1.0 (2013-02-25)
Page 21 of 45
The HLR9820 consists of five logical layers: signaling processing layer, subscriber
data management layer, data service layer, data storage layer, and O&M layer. Each
layer adopts distributed processing. Thus, the whole system features a fully-distributed
structure.
The fully-distributed structure endues the HLR9820 with the following advantages:
High reliability
When any functional entity fails, the load is automatically switched over to other
functional entities. Thus, the service provisioning of the whole system is not
adversely affected.
Smooth expansion
During system expansion, only the related functional entities need to be added.
After detecting that the newly added functional entities are running stably, the
system automatically distributes the load evenly. Thus, the service provisioning
of the system is not adversely affected during the system expansion.
3.2 ATCA-Compatible OSTA 2.0 Hardware Platform

The HLR9820 adopts the ATCA-compatible OSTA 2.0 hardware platform.
Composed of a series of PCI Industrial Computer Manufacturers Group (PICMG3.X)
specifications, the ATCA standards are widely accepted as the standards for the
next-generation, standard telecommunication hardware platforms.
The OSTA 2.0 platform adopts the Intel Architecture (IA), which allows the
high-performance and low-consumption processor, and the Carrier Grade Linux (CGL)
technology. It is a highly competitive server provided by Huawei for
telecommunication and IT markets.
In addition to complying with the ATCA standards, the OSTA 2.0 platform enjoys the
following advantages:
The whole equipment and monitoring equipment comply with the carrier-class
application design.
The service plane, control plane, and management plane are physically separated.
Thus, the lower-layer hardware planes are not adversely affected by other planes.
When the hardware needs to be upgraded, the software can still be used without
any modification. Thus, the system reliability is greatly improved.
The devices used in the OSTA 2.0 platform comply with the device selection
specifications for carrier-class equipment and the ETSI/NEBS standards.
The system is enhanced with the monitoring on equipment running, hardware

components, and external interfaces, and added with the fault diagnosis
mechanism and pre-alert for the subhealth status.
The OSTA 2.0 platform meets the anti-noise requirements and heat dissipation
requirements for carrier-class equipment.
The OSTA 2.0 platform adopts automatic fault detection and fault isolation
technologies. Thus, the fault detected can be isolated and will not adversely affect
the running of other parts.

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

The perfect fault location design allows accurate identification of the faulty
device.
3.3 Memory Data Management Technology

The memory manages all the subscriber data stored in the HLR9820. The board
memory accomplishes the data query and data modification related to service
processing. The external storage device (such as the disk array) of boards only
provides permanent storage of data. It is independent of service processing.
The memory data management endues the HLR9820 the following advantages:
The service processing is independent of the external data storage device of

boards.
If the external data storage device of boards fails, the service processing will not
be adversely affected.
Compared with the data management in hard disks, the memory data
management features higher throughput and shorter time delay. It greatly
enhances the system performance, especially for the large-capacity HLR.
3.4 Multi-Level Data Backup Mechanism

The HLR9820 adopts the multi-level data backup mechanism. The multi-level data
backup mechanism enables subscriber data to be stored in different physical data
storage devices, ensuring the security of subscriber data.
The multi-level data backup comprises:
Level-1 backup
The subscriber data is stored in the memories of different boards. Multiple boards
form a cluster. The data of the master node is synchronized to the slave node.
Level-2 backup
The subscriber data stored in the board memory is backed up to the local hard
disk of the board. Two local hard disks work in RAID 1 mode.
Level-3 backup
The subscriber data stored in the board memory is backed up to the disk array.
The disk array has nine hard disks working in RAID. Hot spare disks are
configured for the hard disks of the disk array.

Issue 1.0 (2013-02-25)
Page 23 of 45
Figure 3-1 Multi-level data backup
Level-1 backup
Slave
Master
Cluster
Level-2 backup
Level-3 backup
Local hard disk
Disk array
3.5 Virtual HLR Function

The virtual HLR function allows a physical HLR to be divided into several logical
HLRs. Each logical HLR is equivalent to the HLR in the local network.
The virtual HLR function enables the local networks in different areas to share the
same physical HLR. It can realize centralized equipment maintenance, and distributed
service processing and subscriber data management.
The virtual HLR function allows authority-based and domain-based management and
helps carriers to provide differentiated services. It facilitates carriers to carry out
network planning and equipment maintenance.
The virtual HLR function can greatly reduce the number of NEs used in the network,
slash the equipment investment, and cut down the investment and expenses arising
from system upgrade and maintenance.
Figure 3-2 illustrates the virtual HLR function.

Issue 1.0 (2013-02-25)
Page 24 of 45
Figure 3-2 Virtual HLR function

Local
network 1
Virtual HLR 1
Local
network 2
Virtual HLR 2
Virtual HLR 3
HLR9820
Local
network 3
3.6 Large Capacity and High Integrity

The HLR9820 provides large capacity and high integrity. It helps carriers to
implement centralized management and to cut down the OPEX.
The large capacity and high integrity feature of the HLR9820 provides the following
benefits:
Slashing the equipment maintenance cost and the maintenance manpower cost
Six cabinets in full configuration can support 100 million subscribers. The large
capacity feature and centralized management minimize the OPEX.
Simplifying operations
Carriers can access all the HLRs (HLRs in an area or a country) through a
provision system. Through the provision system, carriers can provide services,
such as issuing cards, defining subscribers, providing services, and query services,
for subscribers in an area or a country.
Saving network resources

The nearest HLR FE is accessed for call processing. Thus, the transmission over
the signaling network is simplified, and the network resources are saved.
3.7 Separate Data Processing and Service Processing

The HLR9820 consists of the HLR-BE and the HLR-FE. It supports separate
deployment of the data part and the service part.
The separate deployment of the data part and the service part endues the HLR9820
with the following advantages:
Issue 1.0 (2013-02-25)
Page 25 of 45

More flexible networking

The BE and FE can be deployed in different places. Thus, carriers can determine
the number and location of BEs and FEs based on the population distribution and
geographical conditions.
Enhanced system compatibility

The BEs of the HLR9820 provide standard and open data access interfaces,
through which the third-party equipment can access the HLR9820. Thus, carriers
will not have to bother with the problem of interconnecting systems of different
suppliers.
3.8 Physical Self-Redundancy Solutions

Immeasurable loss will be caused if services are interrupted or important data in the
HLR is lost because of maloperations, equipment failures, or natural disasters.
To improve the network security and reliability, Huawei provides the remote HLR
redundancy solution, that is, an HLR is added to the network to work as the
redundancy of the existing HLR. In normal conditions, the active HLR processes
various signaling messages and services. When the active HLR fails, the redundancy
HLR takes over the service processing, thus ensuring uninterrupted service
provisioning over the PLMN.
Huawei provides the following HLR redundancy solutions:
Seamless geographic redundancy solution

In the seamless geographic redundancy solution, the active and the redundancy
HLR are HUAWEI HLR9820 V900 products. The active and redundancy HLRs
work in active/standby mode or in load-sharing mode for service processing or
data processing.
In the seamless geographic redundancy solution, the database synchronization
involves data backup and data consistency check..
Figure 3-3 shows the principle of the database synchronization.
Figure 3-3 Synchronization of the databases
Active HLR
Redundancy HLR
SMF
SCF
SCF
SMF
Master DRU
Slave DRU
Master DRU
Slave DRU
Master DSU
Slave DSU
Master DSU
Slave DSU

Issue 1.0 (2013-02-25)
Page 26 of 45
The active and redundancy HLRs have master and slave nodes. When the data in
the active HLR changes, the master DRU of the redundancy HLR backs up the
data from the master DRU of the active HLR, and the master DSU of the
redundancy HLR backs up the data from the master DSU of the active HLR.
Then, the slave nodes back up the data from the master nodes in the redundancy
HLR.
After the data backup is complete, data consistency check is performed to ensure
data consistency between the active HLR and the redundancy HLR. The data
consistency check is performed on only the master nodes of the active and
redundancy HLRs.
1+1 mated redundancy solution

The 1+1 mated redundancy solution allows two sets of Huawei HLRs to work in
active/standby mode. In the 1+1 mated redundancy solution, either HLR stores
the same subscriber data as an independent HLR. When the active HLR fails, the
redundancy HLR takes over all services from the active HLR.
N+1 mated redundancy solution

The N+1 mated redundancy solution allows the networking of N active HLRs
and one redundancy HLR. All the HLRs are provided by Huawei. Here, N ranges
from 1 to 16. Generally, a maximum of 10 active HLRs are recommended. The
redundancy HLR backs up the data of the active HLRs on a real-time basis. If one
or more active HLRs fail, the redundancy HLR takes over services from the
faulty active HLRs.
N+1 compatibility redundancy solution

The N+1 compatibility redundancy solution allows the networking of N active
HLRs and one redundancy HLR. The active HLRs can be provided by different
vendors, and the redundancy HLR is provided by Huawei. Here, N ranges from 1
to 16. Generally, a maximum of 10 active HLRs are recommended. The
redundancy HLR backs up the data of the active HLRs on a real-time basis. If one
or more active HLRs fail, the redundancy HLR takes over services from the
faulty active HLRs.
3.9 Smooth Data Convergence

The HLR9820 supports smooth evolution towards the USC. It has the capability to
converge various types of service data, such as the service data of the HSS subscribers
and that of the AAA subscribers. It can greatly simplify the data convergence process
of traditional HLRs, laying the foundation for service convergence.
3.10 Standard and Open Data Access Interface

In traditional deployment of new services, carriers have to focus on:
Service logics
Complicated subscriber data management, including:
Data structure design
Data storage
Issue 1.0 (2013-02-25)
Page 27 of 45
Data backup
Data redundancy
Data security mechanism
Data operations
The diversity of equipment provided by different vendors and different data

management mechanisms slow down the development of new services. Failing to
promptly deploying new services hinders carriers from forestalling the competition
predominance.
In addition to the capability of integrating the subscriber data of different services, the
HLR9820 provides a standard and open data access interface, through which the
third-party applications can obtain the subscriber data. This feature greatly slashes the
service deployment cost, simplifies the data complexity caused by the emergence of
new services, and helps carriers to provide new services.
3.11 Comprehensive Data Statistics and Analysis

The HLR9820 backs up the subscriber data to an independent server at the specified
time. Through the independent server, users can query and learn the subscriber data in
detail.
This offline data processing mode helps carriers to learn:
Subscriber data of specific services
Overall subscriber information, including:
Service subscription and development trend
Roaming ratio
Network service features
Based on the information, carriers can learn the network operation, better understand
subscribers' behavior, and adjust market strategies in time. Thus, the HLR9820 can
help carriers to provide tailored services and gain competition predominance.

Issue 1.0 (2013-02-25)
Page 28 of 45
Technical Specifications
4.1 Performance Specifications

Table 4-1 lists the performance specifications of the HLR9820.
Table 4-1 Performance specifications of the HLR9820
Item
Performance Specifications
Maximum subscribers supported
100 million
Bearer networking modes supported
TDM
ATM
IP
Number of TDM 64 kbit/s links

supported
2560
Number of TDM 2 Mbit/s links

supported
320
Number of ATM 2 Mbit/s links

supported
320
Number of M3UA links supported
2496
BNH command processing speed
2,000 pcs/second
NOTE
The full-IN GSM traffic model refers to the GSM traffic model that all the subscribers are
intelligent network (IN) subscribers. See Table 4-2.
Table 4-2 lists the full-IN GSM traffic model. In the GSM traffic model, the parameter
values are calculated based on 100,000 subscribers.

Issue 1.0 (2013-02-25)
Page 29 of 45
Table 4-2 Full-IN GSM traffic model

Parameter
Value (Times/Second/100,000 Subscribers)
SendAuthenticationInfo
10
UpdateLocation
10
SendRoutingInfo
40
SendRoutingInfoForSM
25
GprsUpdateLocation
4.2 Reliability Specifications

Table 4-3 lists the reliability specifications of the HLR9820.
Table 4-3 Reliability specifications of the HLR9820
Item
Reliability Specifications
System repair rate
0.3%
Availability
99.9997%
Fault detection rate
> 95%
Mean time to repair (MTTR)
<1h
Service interruption time of each upgrade or

expansion
< 30 seconds
Average service interruption time in a year
< 5 minutes
Duration from system power-on to service ready
10 minutes
Success rate of the switchover between redundancy

components
> 95%
Time required for the switchover between OSTA 1.0

boards
3 seconds
Time required for the switchover between OSTA 2.0

boards
10 seconds
4.3 Cabinet Specifications

The HLR9820 hardware is installed in Huawei N68E-22 cabinets. Table 4-4 lists the
technical specifications of the N68E-22 cabinet.

Issue 1.0 (2013-02-25)
Page 30 of 45
Table 4-4 Technical specifications of the N68E-22 cabinet

Item
Specifications
Number of cabinets (in full

configuration)
Cabinet model
N68E-22 server cabinet
Power supply
48 V DC
Cabinet dimensions (height x width

x depth)
2,200 mm x 600 mm x 800 mm
Available height in the cabinet
46 U (1 U = 44.45 mm = 1.75 inches)
Weight of the empty cabinet
100 kg
Weight of the fully-loaded

integrated cabinet
304 kg

extended cabinet (2 OSTA 1.0+1
OSTA 2.0)
277 kg

extended cabinet (1 OSTA 1.0+2
OSTA 2.0)
331 kg
Load-bearing capacity of the

equipment room floor
600 kg/m2
Floor space
2.88 m2
Heat dissipating capacity
12771.8 BTU
Cabling modes supported
Upward cabling
Downward cabling
4.4 Power Consumption

Table 4-5 lists the power consumption of the HLR9820.
Table 4-5 Power consumption of the HLR9820
Cabinet
Power Consumption (W)
Integrated cabinet (in full configuration)
3,213W
Extended cabinet (in full configuration 2 OSTA

1.0+1 OSTA 2.0)
3,218W

Issue 1.0 (2013-02-25)
Page 31 of 45
Extended cabinet (in full configuration 1 OSTA

1.0+2 OSTA 2.0)
4,679W
OSTA 1.0 subrack (in full configuration)
579W
OSTA 2.0 subrack (in full configuration)
2,040 W
KVMS
24 W
FE LAN switch
35 W
GE LAN switch
90 W
Disk array
300 W
4.5 Clock Specifications

Table 4-6 lists the technical specifications of the clock system used in the HLR9820.
Table 4-6 Technical specifications of the HLR9820 clock system
Item
Specifications
Clock
network
access
parameter
Minimum
accuracy
Stratum-2 clock: 4 x 10-7
Pull-in range
Synchronization accuracy of stratum-2 clock: 4 x 10-7
Stratum-3 clock: 4.6 x 10-6
Synchronization accuracy of stratum-3 clock: 4.6 x

10-6
Long-term
phase
variation
Maximum
frequency offset
Stratum-2 clock: 5 x 10-10/day
Initial maximum
frequency offset
Stratum-2 clock: < 5 x 10-10/day
Ideal working
status
MRTIE 1ms
Holdover working
status
MRTIE (ns) a x s + (1/2) x b x s2 + c
Stratum-3 clock: 2 x 10-8/day

Stratum-3 clock: < 1 x 10-8/day
Here, s stands for the time in seconds, and MRTIE is in

nanosecond (ns).
Stratum-2 clock:
a = 0.5, b = 1.16 x 10-5, c = 1000
Stratum-3 clock:
a = 10, b = 2.3 x 10-4, c = 1000

Issue 1.0 (2013-02-25)
Page 32 of 45
Clock
working
mode
Input jitter
tolerance
Fast pull-in
Locked
Holdover
Free run
See Figure 4-1.
Lowest accuracy: the maximum frequency offset in a long period (20 years) when the
external reference frequency is unavailable (when the clock works in free-run mode)
Maximum frequency offset: the maximum relative difference between the clock frequencies
in one unit of time during the continuous running of the clock
Pull-in range: the maximum bandwidth of the input signal that the clock system can locks
MRTIE: maximum relative time interval error, the variation of maximum peak-to-peak
delay of a tested clock relative to an actual reference clock within the test time
Figure 4-1 shows the input jitter tolerance of the clock system.
Figure 4-1 Maximum allowed input jitter and lower threshold of wander
Y (UI)
10
Peak-peak jitter and wander amplitude (log scale)
A 0 =36.9
10 1
Slope coefficient is 20 dB/10

times sound interval
A1=1.5
1
A2=0.2
10 -1
1.2 10- 5 10
X
20
2.4 k
18 k
100 k
f (Hz)
If the system can still work normally when the jitter frequency of an input signal is 1
kHz and the signal amplitude is more than 1.5 UI, you can infer that the input signal
satisfies requirements.
UI stands for unit interval. The reciprocal of the digital signal frequency is one UI. For example,
the UI of a 2.048 Mbit/s signal is 488 ns.

Issue 1.0 (2013-02-25)
Page 33 of 45
4.6 EMC Specifications

The HLR9820 complies with the following electromagnetic compatibility (EMC)
standards:
EN 55022 class A
CISPR 22 class A
ETSI EN 300 386
GB9254 class A
4.7 Environment Requirements

This section describes the environment requirements for the HLR9820. The
environment requirements are based on the following standards:
GB 4798 Environmental conditions existing in the application of electric and

electronic products
ETS 300019 Equipment Engineering (EE); Environmental conditions and

environmental tests for telecommunications equipment
IEC 60721 Classification of environmental conditions
The environment requirements comprise the requirements for:

Storage Environment
Transportation Environment
Operation Environment
4.7.1 Storage Environment

This section describes the requirements for the storage environment of the HLR9820.
It consists of:
Climatic Requirements
Waterproof Requirements
Biological Requirements
Air Purity Requirements
Mechanical Stress Requirements
Table 4-7 lists the climatic requirements for equipment storage.
Table 4-7 Climatic requirements for equipment transportation
Item
Range
Temperature
40C to +70C
Relative humidity
10% to 100%
Issue 1.0 (2013-02-25)
Page 34 of 45
Altitude
5000 m
Air pressure
70 kPa to 106 kPa
Temperature change rate
1C/min
Solar radiation
1120 W/m2
Heat radiation
600 W/m2
Wind speed
20 m/s
Generally, the equipment must be stored indoors.
Indoor storage
The floor where the equipment is placed must be protected against water. In
addition, the equipment must be protected against water from the auto
fire-fighting device and the air-conditioner.
Outdoor storage
If the equipment has to be placed outdoors, ensure that:
The crates are not damaged.
Waterproofing measures are taken to protect the crates against rain.
The floor where the crates are placed must be protected against water.
The crates are not exposed to direct sunlight.
Ensure that the storage area is protected against epiphyte or mildew and rodents.

The equipment must be stored in the environment that is free from explosive,
conductive, and magnetic conductive or corrosive dust.
Table 4-8 lists the air purity requirements for physically active substances.
Table 4-8 Air purity requirements for physically active substances in equipment storage
Physically Active Substances
Density
Diameter
Suspended dust
5.00 mg/m
75 m
Falling dust
20.0 mg/mh
75 m diameter 150 m
Sand
300 mg/m
150 m diameter 1000 m
Table 4-9 lists the air purity requirements for chemically active substances.
Issue 1.0 (2013-02-25)
Page 35 of 45
Table 4-9 Air purity requirements for chemically active substances in equipment storage
Chemically Active Substances
Density (mg/m3)
SO2
0.3 to 1.0
H2S
0.1 to 0.5
NO2
0.5 to 1.0
NH3
1.0 to 3.0
Cl2
0.1 to 0.3
HCl
0.1 to 0.5
HF
0.01 to 0.03
O3
0.05 to 0.1

Table 4-10 lists the mechanical stress requirements for equipment storage.
Table 4-10 Mechanical stress requirements for equipment storage
Item
Sub-Item
Range
Sinusoidal
vibration
Motion
7.0 mm
Acceleration
20.0 m/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
Impact response
spectrum II
250 m/s
Static payload
5 kPa
Unsteady impact
NOTE
Impact response spectrum: the maximum acceleration response curve generated by the equipment
under the specified impact excitation(Impact response spectrum II means that the duration of the
semi-sine impact response spectrum is 6 ms.)
Static payload: the total force that the equipment in the packages piled in the specified way can bear
from the top
4.7.2 Transportation Environment

This section describes the requirements for the transportation environment of the
HLR9820. It consists of:
Issue 1.0 (2013-02-25)
Page 36 of 45

Table 4-11 lists the climatic requirements for equipment transportation.
Table 4-11 Climatic requirements for equipment transportation
Item
Range
Temperature
40C to +70C
Relative humidity
10% to 100%
Altitude
5000 m
Air pressure
70 kPa to 106 kPa
3C/min
Solar radiation
1120 W/m2
Heat radiation
600 W/m2
Wind speed
20 m/s
During the transportation of the HLR9820, ensure that:
The package is intact.
Waterproof measures are taken to prevent rain from soaking into the package.
The vehicle has no water accumulated inside.
Ensure that the transportation vehicle is protected against epiphyte or mildew and
rodents.

The air must be free from explosive, conductive, and magnetic conductive or corrosive
dust.

Issue 1.0 (2013-02-25)
Page 37 of 45
Table 4-12 Air purity requirements for physically active substances in equipment
transportation
Density
Diameter
Suspended dust
75 m
Falling dust
3.0 mg/mh
75 m diameter 150 m
Sand
100 mg/m
Table 4-13 Air purity requirements for chemically active substances in equipment
transportation
Density (mg/m3)
SO2
0.3 to 1.0
H2S
0.1 to 0.5
NO2
0.5 to 1.0
NH3
1.0 to 3.0
Cl2
0.1 to 0.3
HCl
0.1 to 0.5
HF
0.01 to 0.03
O3
0.05 to 0.1

Table 4-14 lists the mechanical stress requirements for equipment transportation.
Table 4-14 Mechanical stress requirements for equipment transportation
Item
Sub-Item
Range
Sinusoidal
vibration
Motion
7.5 mm
Acceleration
20.0 m/s
40.0 m/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
200 Hz to 500 Hz
Acceleration
spectrum density
10 m/s
3 m/s
1 m/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
200 Hz to 500 Hz
Random
vibration

Issue 1.0 (2013-02-25)
Page 38 of 45
Unsteady
impact
Impact response
spectrum II
300 m/s
Static payload
10 kPa
NOTE
under the specified impact excitation (Impact response spectrum II means that the duration of the
from the top
4.7.3 Operation Environment

This section describes the requirements for the operation environment of the HLR9820.
It consists of:
Shockproof Requirements
Anti-Noise Requirements
Table 4-15 lists the climatic requirements for system running.
Table 4-15 Climatic requirements for system running
Item
Range
Temperature
Long-term operation temperature: +5C to +40C

Short-term operation temperature: -5C to +45C
Relative humidity
Long-term operation humidity: 45% to 75%

Short-term operation humidity: 5% to 95%
Altitude
4000 m
Air pressure
70 kPa to 106 kPa
15C/min
Solar radiation
700 W/m2
Heat radiation
600 W/m2
Wind speed
1 m/s

Issue 1.0 (2013-02-25)
Page 39 of 45
Ensure that the HLR9820 is running in an environment that is protected against
epiphyte or mildew and rodents.

The air must be free from explosive, conductive, and magnetic conductive or corrosive
dust.
Table 4-16 Air purity requirements for physically active substances in system running
Density
Diameter
Suspended dust
0.24mg/m3
75 m
Falling dust
1.5 mg/mh
75 m diameter 150 m
Sand
30 mg/m
Table 4-17 Air purity requirements for chemically active substances in system running
Density (mg/m3)
SO2
0.3 to 1.0
H2S
0.1 to 0.5
NO2
0.5 to 1.0
NH3
1.0 to 3.0
Cl2
0.1 to 0.3
HCl
0.1 to 0.5
HF
0.01 to 0.03
O3
0.05 to 0.1

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

Table 4-18 lists the mechanical stress requirements for system running.
Table 4-18 Mechanical stress requirements for system running
Item
Sub-Item
Range
Sinusoidal
vibration
Motion
3.5 mm
Acceleration
10.0 m/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
Impact response spectrum

II
100 m/s
Static payload
10k Pa
Unsteady
impact
NOTE
under the specified impact excitation (Impact response spectrum II means that the duration of the
from the top
Shockproof Requirements
The HLR9820 complies with the ETS 300 019-2-4-AMD standards.
Anti-Noise Requirements
The sound power noise is smaller than 7.2 bel. The reference standard is EST 300
753, and the test standard is ISO7779.

Issue 1.0 (2013-02-25)
Page 41 of 45
Acronyms and Abbreviations
A
AAA
Authentication, Authorization and Accounting
ARPU
Average Revenue Per User
AS
Application Server
ATCA
Advanced Telecommunications Computing Architecture
ATI
Any Time Interrogation
ATM
Asynchronous Transfer Mode
AuC
Authentication Center
B
SAU
Signaling Access Unit
BAM
Back Administration Module
BE
Back End
BSS
Base Station System
C
CAMEL
Customized Applications for Mobile Network Enhanced Logic
CGL
Carrier Grade Linux
CRBT
Color Ring Back Tone
CS
Circuit Switched
CSCF
Call Session Control Function

Issue 1.0 (2013-02-25)
Page 42 of 45
D
DC
Direct Current
DRU
Data Routing Unit
DSU
Data Service Unit
E
EIR
Equipment Identity Register
EMC
Electromagnetic Compatibility
F
FE
Front End
G
GGSN
Gateway GPRS Support Node
GMLC
Gateway Mobile Location Center
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
GUI
Graphical User Interface
GUP
General User Profile
H
HLR
Home Location Register
HSS
Home Subscriber Server
I
IA
Intel Architecture
IM
Instant Messaging
IMS
IP Multimedia Subsystem
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
IPMB
Intelligent Platform Management Bus

Issue 1.0 (2013-02-25)
Page 43 of 45
M
MAP
Mobile Application Part
MGCF
Media Gateway Control Function
MML
Man-Machine Language
MMS
Multimedia Messaging Service
MNP
Mobile Number Portability
MSC
Mobile Switching Center
N
NEBS
Network Equipment Building Specification
NMS
Network Management System
O
ODB
Operator Determined Barring
OPEX
Operating Expenditure
OSTA
Open Standards Telecom Architecture
P
PICMG
PCI Industrial Computer Manufacturers Group
PS
Packet Switched
PSTN
Public Switched Telephone Network
S
SAU
Signaling Access Unit
SCF
Service Control Function
SCP
Service Control Point
SGSN
Serving GPRS Support Node
SMC
Short Message Center
SMF
Subscriber Management Function
SMU
Subscriber Management Unit

Issue 1.0 (2013-02-25)
Page 44 of 45
SSP
Service Switching Point
T
TCAP
Transaction Capabilities Application Part
TDM
Time Division Multiplex
U
UL
Underwriters Laboratories Inc
UMTS
Universal Mobile Telecommunications System
USC
Unified Subscriber Centre
UTRAN
UMTS Terrestrial Radio Access Network
V
VLR
Visitor Location Register

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

Railway Operational Communication Solution GSM-R HLR9820 Product Description1.0 (20090512)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Railway Operational Communication Solution GSM-R HLR9820 Product Description1.0 (20090512)

Caricato da

Copyright:

Formati disponibili

GSM-R HLR9820 Product Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

GSM-R HLR9820 Product Description

2 Overview of the HLR9820 ............................................................................................... 11

3 System Features ................................................................................................................. 21

4 Technical Specifications .................................................................................................. 29

5 Acronyms and Abbreviations ......................................................................................... 42

GSM-R HLR9820 Product Description

1.1 Huawei USC Solution

Figure 1-1 illustrates Huawei USC solution.

Huawei Proprietary and Confidential

GSM-R HLR9820 Product Description

Figure 1-1 Huawei USC solution

AAA: Authentication, Authorization

AS: Application Server

BE: Back End

CSCF: Call Session

FE: Front End

The implementation of Huawei USC solution comprises three phases:

GSM-R HLR9820 Product Description

Phase I: network simplification

Phase II: data convergence

Phase III: service innovation

1.2 Product Orientation of the HLR9820

AAA: Authentication, Authorization

AS: Application Server

BE: Back End

CSCF: Call Session Control Function

FE: Front End

MGCF: Media Gateway Control Function

MSC: Mobile Switching Center

Huawei Proprietary and Confidential

GSM-R HLR9820 Product Description

SCP: Service Control Point

SGSN: Serving GPRS Support Node

Huawei Proprietary and Confidential

GSM-R HLR9820 Product Description

FE: Front End

GMLC: Gateway Mobile Location Center

1.3 Major Functions of the HLR9820

Subscriber Data Management

Support of the Call-Related Processing

Support of the ATI

Functions of the AuC

Subscriber Data Management

Basic subscriber data

Basic services provided to subscribers

Supplementary services provided to subscribers

Operator-determined barring (ODB) services provided to subscribers

CAMEL services provided to subscribers

GPRS services provided to subscribers

Mobility management in the CS domain

Issue 1.0 (2013-02-25)

GSM-R HLR9820 Product Description

Mobility management in the PS domain

GPRS routing area update

GPRS routing area cancellation

Support of the Call-Related Processing

Support of the ATI