Sie sind auf Seite 1von 44

HLR AC EIR Architecture

HLR AC EIR Architecture

Content
HLR AC EIR Architecture 1
1 Objectives 3
2 Overview 5
2.1 Home Location Register (HLR) 6
2.2 Authentication Centre (AUC) 7
2.3 Equipment Identity Register (EIR) 8
3 Architecture 9
3.1 Block diagram of the DX 200 HLR 10
3.2 Capacity of DX HLR 12
3.3 HLR Cabinets 13
4 Units in DX 200 HLR/AC/EIR i-series 21
4.1 ACU - Authentication Center Unit 22
4.2 BDCU - Basic Data Communications Unit 23
4.3 CMM - Central Memory and Marker 24
4.4 CLSU - Clock System Unit 25
4.5 CLBU - Clock and Alarm Buffer Unit 26
4.6 CCSU - Common Channel Signaling Unit 27
4.7 DBDU - Database Distributor Unit 28
4.8 EMU - Equipment Main Unit 29
4.9 EIRU - Equipment Identity Register Unit 30
4.10 ET - Exchange Terminal (ET16 & ETS2) 31
4.11 GSW 2KB - Group Switch 2KB 33
4.12 HLRU - Home Location Register Unit 34
4.13 OMU - Operation and Maintenance Unit 35
4.14 STU - Statistical Unit 36
5 Evolution towards Subscriber Data Management (SDM) solution 37
6 HLR Innovation 39

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
1
HLR AC EIR Architecture

CN34014EN41GLN0
2 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

1 Objectives
After completing this module, the student should be able to:
• List the main functions of HLR/AC/EIR.
• List the functional units of HLR.
• Describe the physical realization, including plug-in units and the interfaces of these
units.
• List the redundancy principles for the units in HLR.
• Overview HLR innovation (HLRi)

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
3
HLR AC EIR Architecture

CN34014EN41GLN0
4 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

2 Overview
The Nokia Siemens Networks DX HLR consists of HLR, Authentication Centre
(AUC), and Equipment Identity Register (EIR).

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
5
HLR AC EIR Architecture

2.1 Home Location Register (HLR)


The HLR stores the subscribers' GSM/GPRS/UMTS subscription related data. It
offers services for both Circuit Switched (CS) and Packet Switched (PS) networks.
With the 2G/3G common core network, the HLR maintains mobility information,
Intelligent Network (IN) service triggers, and standardized supplementary service
data. The HLR stores subscriber data permanently and provides subscriber data to
the MSC/VLR and/or the SGSN of the area where the mobile is currently located (the
MSC/VLR or the SGSN where the mobile is registered). The HLR also stores the
address of the MSC/VLR and the SGSN where the mobile is registered and provides
the routing information to the requesting entities, for example, to the Gateway MSC
(GMSC).

CN34014EN41GLN0
6 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

2.2 Authentication Centre (AUC)


In GSM/UMTS/LTE networks, special attention is paid to security aspects: security
against forgery and thefts, security of identity transmission, and security of speech
and data transmission. The high level of security is achieved with the Authentication
Centre (AUC).
The AUC handles the management of security data for the authentication of
subscribers. It encrypts and stores the encrypted individual secret keys (K/Ki) of the
home network subscribers in the AUC databases. The AUC generates authentication
vectors requested by the MSC/VLR or the SGSN, using authentication algorithms.
The authentication procedure is performed to validate the correctness of the mobile
user's USIM/SIM card and to prevent accessing the network with a fake card.
For GSM subscribers the AUC generates authentication vectors, triplets, using A3
and A8 cryptographic algorithms that can be customer-specific.
In the UMTS system the authentication is mutual, that is, the network authenticates
the subscriber and the subscriber authenticates the network. The AUC generates the
authentication quintets using f1-f5 algorithms customized by operator-specific
parameters. To support roaming from the UMTS to the GSM, quintets can be
converted into triplets in the AUC.

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
7
HLR AC EIR Architecture

2.3 Equipment Identity Register (EIR)


The Equipment Identity Register (EIR) contains the databases and maintains the
database records of International Mobile Equipment Identification (IMEI) numbers.
These IMEI numbers are stored on three lists. The lists, white, grey, and black,
indicate the current status of the mobile equipment: the white list indicates approved
mobile equipment in good standing, while the grey list indicates mobiles under
observation, such as for suspected malfunction. The black list includes equipment
with, for example denied access to the network, such as stolen or missing mobile
phones. IMEI checking is executed to find out if the mobile equipment can be found
on some of the lists or if it is completely unknown in the EIR. Depending on the IMEI
check result, the requesting party can decide on further actions.
When the EIR receives a request from the MSC/VLR (or SGSN or MME), it searches
its databases to determine on which list a mobile phone's IMEI is located. It then
sends the information back to the MSC/VLR, which acts on the information
accordingly; for example, the MSC/VLR may terminate the call if the mobile phone's
IMEI is found on the black list.

DX HLR
DX HLR consist of :
 HLR
 The HLR stores subscriber data permanently and provides subscriber
data to the MSC/VLR of the area where the mobile is currently
located.

 AUC
 The AUC handles the management of security data for the
authentication. It encrypts and stores the encrypted individual secret
keys (K/Ki) of the subscribers in the AUC databases.

 EIR
 The EIR contains the databases and maintains the database records
of International Mobile Equipment Identification (IMEI) numbers.

Fig. 1 DX HLR Overview

CN34014EN41GLN0
8 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

3 Architecture
The figure below shows an overview of the GSM / UMTS network and the position of
the HLR in the network.

2G/3G Network Subsystem

Fig. 2 Overview of the GSM / UMTS Network

The architecture of the DX 200 HLRi/ACi/EIRi is similar to the MSCi/VLRi. It is


designed with a modular software and hardware structure. Its functions are divided
among several functional entities, called functional units.
In the presented document the terms DX 200 HLRi are used to denote the DX 200
HLRi/ACi/EIRi. Figure below presents the block diagram of the DX 200 HLRi.

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
9
HLR AC EIR Architecture

3.1 Block diagram of the DX 200 HLR


The HLR is based on the same DX 200 hardware that is used in the other network
elements as well. Some of the elements of the HLR are the fast MB (Message Bus)
connecting the dedicated processor units, the GSW (Group Switch) for switching the
signaling channels to the signaling links, and the ETs (Exchange Terminals) to
interface with the transmission systems.
The new DX HLR is delivered with two alternative hardware architectures: TDM and
IP connectivity based variants. The IP connectivity based architecture is optimized to
utilize the Internet Protocol based LAN interfaces and it does not offer the TDM
based connectivity.

DX HLR TDM architecture

Fig. 3 DX HLR TDM (dataful) architecture

CN34014EN41GLN0
10 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

DX HLR IP Architecture

Fig. 4 DX HLR IP architecture

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
11
HLR AC EIR Architecture

3.2 Capacity of DX HLR


The HLR with the new mechanics (cabinet IC209-B with forced ventilation) has the
total capacity of 10 million subscribers. The capacity is distributed among normal
subscribers, telemetric subscribers and MultiSIM groups.
The maximum subscriber capacity of the HLR (10 million subscribers) can be built
gradually in steps as the number of subscribers in the network increases. The
subscriber capacity can be increased in steps of 1 000 000 (hardware) and 5 000
(software) subscribers.
The maximum static capacity of the AUC database is 20 million subscriber entries.
The EIR database can store 4 million grey list IMEI entries, 20 million black list
entries, and 200000 white list entries. Each white list IMEI entry can hold an IMEI
series of up to 1 million IMEIs. Each grey or black list entry can be either a single
IMEI or an IMEI series of up to 1 000 IMEIs. An IMEI series is an unbroken sequence
of consecutive IMEI numbers that is defined by the first and last IMEI in the series.
The virtual subscriber capacity is 3 million.

Capacity of the HLR Database

Database Maximum capacity

HLR 10,000,000

AC 20,000,000

EIR White list:


200,000 IMEI entries (1…1,000 IMEIs/entry)
Grey list:
4 million IMEI entries (1…1,000 IMEIs/entry)
Black list:
20 million IMEI entries (1…1,000 IMEIs/entry)

Fig. 5 Capacity of the HLR Database

CN34014EN41GLN0
12 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

3.3 HLR Cabinets


The HLR has two alternative HW configurations: TDM and IP connectivity based.
The HLR IP includes two base cabinets:
• 14HC (CCC, Cable Conduit Cabinet included)
• 14BC
The HLR IP can be expanded with 14IC cabinets to bring more subscriber data
storage capacity.
The HLR TDM includes two base cabinets:
• 14HC (CCC, Cable Conduit Cabinet included)
• 14CC (CCC, Cable Conduit Cabinet included)
The HLR TDM can be expanded with 14EC cabinet to bring more TDM connectivity
and with 14IC cabinets to bring more subscriber data storage capacity.
These cabinet types are used in M14 first deliveries and they are not compatible with
earlier deliveries. Depending on whether the configuration is IP or TDM-based,
different cabinets are used. The 14HC cabinet is used in all configurations.
The HLRi can be upgraded to system level M14 from earlier releases. The Ethernet-
based Message Bus can be implemented on in M14 first deliveries.

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
13
HLR AC EIR Architecture

HLR Cabinets in M14

The HLR has two alternative HW configurations: TDM and IP connectivity


based.

The HLR IP includes two base cabinets:


 14HC (CCC, Cable Conduit Cabinet included)
 14BC
The HLR IP can be expanded with 14IC cabinets to bring more subscriber
data storage capacity.

The HLR TDM includes two base cabinets:


 14HC (CCC, Cable Conduit Cabinet included)
 14CC (CCC, Cable Conduit Cabinet included)
The HLR TDM can be expanded with 14EC cabinet to bring more TDM
connectivity and with 14IC cabinets to bring more subscriber data storage
capacity.

Fig. 6 HLR Cabinet configuration

CN34014EN41GLN0
14 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

The HLR IP Cabinets

Fig. 7 The HLR IP (dataful) cabinets

The HLR TDM Cabinets

Fig. 8 The HLR TDM (dataful) cabinets

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
15
HLR AC EIR Architecture

3.3.1 Release M14 H Cabinet (14HC)


The release M14 H cabinet contains the units controlling the equipment and
subscriber identity databases. The network element always has one M14 H cabinet.
The 14HC data full cabinet configuration includes:
• one Authentication Center Unit (ACU) pair, complete with dedicated storage
devices installed in the same cartridge
• one Central Memory and Marker unit (CMM) pair
• two duplicated Clock Buffer Units (CLBU) installed in CLAC-B cartridges
• two SWU unit pairs, housed in LANU cartridges
• one Operation and Maintenance Unit (OMU) pair, complete with storage devices
installed in a separate cartridge
• one Database Distributor Unit (DBDU) pair, complete with dedicated storage
devices installed in the next cabinet
• one Statistical Unit (STU) pair
• three Equipment Identity Register Units (EIRU)
• one Home Location Register Unit (HLRU) pair, each complete with dedicated
storage devices installed in a separate cartridge
• four Fan Tray Units (FTRB-A) to ensure forced ventilation

14HC cabinet

Fig. 9 Equipment in the 14HC cabinet in the data full HLRi

CN34014EN41GLN0
16 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

3.3.2 Release M14 B Cabinet (14BC)


The release M14 B cabinet includes most of the signaling units of the HLR IP
configurations, along with some database units. The network element 14BC cabinets
are used in IP data full and data less configurations. The 14BC cabinet in data full
configuration includes:
• twenty Signaling Units (SIGU)
• one Home Location Register Unit (HLRU) pair and storage devices
• two duplicated Clock Buffer Units (CLBU) installed in CLAC-B cartridges
• one Equipment Main Unit (EMU) pair
• two Base Data Communications Units (BDCU)
• two SWU unit pairs for control LAN, housed in LANU cartridges
• four Fan Tray Units (FTRB-A) to ensure forced ventilation

14BC cabinet

Fig. 10 Equipment in the 14BC cabinet in the HLRi data full configuration

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
17
HLR AC EIR Architecture

3.3.3 Release M14 I Cabinet (14IC)


The release M14 I cabinet contains the units that handle the key operation and
maintenance tasks. The network element can have one or two 14IC extension
cabinets depending on configuration. The 14IC cabinet can include in its maximum
configuration:
• two Authentication Center Unit (ACU) pairs, complete with dedicated storage
devices installed in a separate cartridge
• two duplicated Clock Buffer Units (CLBU) installed in CLAC-B cartridges
• one SWU unit for register LAN, housed in LANU cartridges
• four Home Location Register Unit (HLRU) pairs
• four Fan Tray Units (FTRB-A) to ensure forced ventilation

14IC cabinet

Fig. 11 Equipment in the M14IC cabinet in the HLRi

CN34014EN41GLN0
18 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

3.3.4 Release M14 C Cabinet (14CC)


The release M14 C cabinet contains the Group Switch Matrices of the HLRi TDM
configurations, along with some database units. The network element always has
one M14 C cabinet in TDM-based configurations. The 14CC data full configuration
includes:
• eight Signaling Units (*SU) (configurable as CCSU or SIGU)
• one Group Switch unit (GSW2KB) pair
• two GT4C-A cartridges equipped with one ETS2 plug-in unit and up to six ET16
plug-in units each
• two duplicated Clock Buffer Units (CLBU) installed in CLAC-B cartridges
• one Equipment Main Unit (EMU) pair and storage devices
• two Base Data Communications Units (BDCU)
• one Home Location Register Unit (HLRU) pair
• Database Distributor Unit (DBDU) mass memory pair (SD DBDU)
• one SWU unit pair for control LAN, housed in LANU cartridges
• four Fan Tray Units (FTRB-A) to ensure forced ventilation

14CC cabinet

Fig. 12 Equipment in the 14CC cabinet in the data full HLRi

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
19
HLR AC EIR Architecture

3.3.5 Release M14 E Cabinet (14EC)


The release M14 E cabinet contains the signaling unit expansion board of the HLRi
TDM configuration. The network element can have an optional 14EC cabinet in TDM
configurations. The 14EC includes in its maximum configuration:
• twenty-six Signaling Units (*SU) (configurable as CCSU or SIGU)
• two duplicated Clock Buffer Units (CLBU) installed in CLAC-B cartridges
• two SWU unit pairs for control LAN, housed in LANU cartridges
• four Fan Tray Units (FTRB-A) to ensure forced ventilation

14EC cabinet

Fig. 13 Equipment in the 14EC cabinet in the HLRi

CN34014EN41GLN0
20 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4 Units in DX 200 HLR/AC/EIR i-series

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
21
HLR AC EIR Architecture

4.1 ACU - Authentication Center Unit


Redundancy: 2n
Purpose: The ACU is responsible for the storage of the authentication data. It
also provides authentication triplets for user authentication and
performs the speech encryption functions.
Type: Computer Unit, with a dedicated storage device unit as a subunit

Authentication Center Unit (ACU)

Function: The ACU is


responsible for the storage of
the authentication data. It
also provides authentication
triplets for user
authentication and performs
the speech encryption
functions.

Redundancy: 2n

Fig. 14 ACU in a CC3C-A cartridge (with SECMO-C)

CN34014EN41GLN0
22 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.2 BDCU - Basic Data Communications Unit


Redundancy: None; redundancy of the OSI/LAN connection is achieved using OSI
management. The HLRi always features two BDCUs.
Purpose: The BDCU contains all communication links to the O&M network, to
the billing center (BC) and to the CEIR. One BDCU can handle a
maximum of five connections.
The BDCU provides the following external interfaces:
• analogue X.25
• digital X.25
• LAN/Ethernet
Type: Computer Unit with no subunits

Basic Data Communications Unit (BDCU)

Function: The BDCU contains


all communication links to
the O&M network, to the
billing center (BC) and to the
CEIR. One BDCU can
handle a maximum of five
connections.
The BDCU provides the
following external interfaces:
-analog X.25
-digital X.25
-LAN/Ethernet

Redundancy: n

Fig. 15 BDCU in a CC3C-A cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
23
HLR AC EIR Architecture

4.3 CMM - Central Memory and Marker


Redundancy: 2n
Purpose: The CMM handles the functions of two different functional entities,
the Central Memory and the Marker.
The central memory handles the routing functions of the HLRi. It also
contains all system configuration data and master copies of
distributed files. In addition, it is responsible for the central functions
of CCS7.
The Marker controls and supervises the GSW, hunts for free circuits
and is responsible for establishing and releasing all connections. The
Marker and the GSW make up a switchover entity, which is
duplicated for 2n redundancy.
Type: Computer Unit with GSW2KB as a subunit

Central Memory and Marker (CMM)

Function:The CMM handles the


functions of two different
functional entities, the
Central Memory and the
Marker.

Redundancy: 2n

Fig. 16 CMM in a DC3C-B cartridge

CN34014EN41GLN0
24 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.4 CLSU - Clock System Unit


Redundancy: 2n, n=1. The HLRi always features two independent CLSUs, which
are placed in the same cartridge.
Purpose: The CLSUs generate the clock signals necessary for synchronizing
the functions of the HLRi and transmit them further to the CLBUs in
the other cabinets. When using hierarchical mode, each unit is
synchronized to up to four inputs (ETs), usually coming from the
PSTN. The CLSUs also feed the timing signals to, and collect the
wired alarms from the units in the 14HC and send them further to the
OMU. One CLSU can handle the timing and alarm collection
functions of up to 15 cartridges.
Type: Functional unit with no subunits

Clock System Unit (CLSU)

Function:
The CLSUs generate the clock signals
necessary for synchronising the
functions of the HLRi and transmit
them further to the CLBUs in the other
cabinets.
The CLSUs also collect the wired alarms
from the units in the 14HC and send
them further to the OMU.

Redundancy: 2n

Fig. 17 Two independent CLSUs in a CLOC-B/CLOC-A cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
25
HLR AC EIR Architecture

4.5 CLBU - Clock and Alarm Buffer Unit


Redundancy: 2n
Purpose: The duplicated CLBUs distribute the clock signals (generated by the
CLSUs) to the units in the same cabinet. The CLBU also collects the
wired alarms from the units whose timing it handles and transfers
them further to the OMU. One CLBU unit can handle the timing and
alarm collection functions of up to 15 cartridges.
Type: Functional unit with no subunits

Clock and Alarm Buffer Unit (CLBU)

Function:
The CLBUs distribute the clock signals
(generated by the CLSUs) to the units
in the same cabinet.
The CLBU also collects the wired alarms
from the units whose timing it handles
and transfers them further to the OMU.

Redundancy: 2n

Fig. 18 Two independent CLBUs in a CLAC-B/CLAC-A cartridge

CN34014EN41GLN0
26 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.6 CCSU - Common Channel Signaling Unit


Redundancy: n+1,
Purpose: The CCSU handles CCS7 signaling between HLR and MSS. CCS7
signaling traffic can be carried over both PCM lines (TDM) and the IP
network with SIGTRAN.
It also controls the PCM connections of the network element and the
ETs allocated to the BDCU.
Type: Computer unit with no subunits

Common Channel Signalling Unit (CCSU)

Function:
The CCSU handles CCS7 signalling
between HLR and MSS. CCS7
signalling traffic can be carried over
both PCM lines (TDM) and the IP
network with SIGTRAN.
The CCSU also controls the PCM
connections of the network element
and the ETs allocated to the BDCU.

Redundancy: n+1

Fig. 19 CCSU in a DC3C-B cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
27
HLR AC EIR Architecture

4.7 DBDU - Database Distributor Unit


Redundancy: 2n
Purpose: The main responsibility of the DBDU is to distribute HLR/AC
subscriber related data to the correct unit (HLRU/ACU). This
information can come from either the network or the administrative
unit.
Type: Computer Unit, with a dedicated storage device unit as a subunit.

Database Distributor Unit (DBDU)

Function:The main responsibility of


the DBDU is to distribute HLR/AC
subscriber related data to the
correct unit (HLRU/ACU).

Redundancy: 2n

Fig. 20 DBDU in a DC3C-B cartridge

CN34014EN41GLN0
28 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.8 EMU - Equipment Main Unit


Redundancy: 2n
Purpose: The EMU contains the main database of the EIRU. The key
responsibilities of the EMU are EIR management and CEIR-EIR
interface management.
Type: Computer Unit with a dedicated storage device unit.

Equipment Main Unit (EMU)

Function:The EMU contains the


main database of the EIRU. The
key responsibilities of the EMU
are EIR management and CEIR-
EIR interface management.

Redundancy: 2n

Fig. 21 EMU in a DC3C-B cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
29
HLR AC EIR Architecture

4.9 EIRU - Equipment Identity Register Unit


Redundancy: n+1/L, max 7 EIRUs
Purpose: The EIRU performs the verification of equipment identities and
provides the network operator with lists of suspicious, stolen or faulty
mobile equipment.
Type: Computer Unit with no subunits

Equipment Identity Register Unit (EIRU)

Function:The EIRU performs


the verification of equipment
identities and provides the
network operator with lists of
suspicious, stolen or faulty
mobile equipment.

Redundancy: n+1/L

Fig. 22 EIRU in a MC2C-A cartridge

CN34014EN41GLN0
30 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.10 ET - Exchange Terminal (ET16 & ETS2)


Redundancy: none
Purpose: The ET performs the electrical synchronization and adaptation of
external PCM lines. The ET is able to do the HDB3 coding and
decoding, insert the alarm bits in the outgoing direction and produce
the PCM frame structure.
At system level M14, ET16 is introduced, which increases the
capacity up to 16 PCM lines in one card. The PCM connections are
on the back plane. This is the most effective way to handle the
cabling arrangements, although it sets the requirement to have the
cabling panel in all network elements using the ET16.
The ET16 interface can be used in the MSS with the optional TDM
cabinet. The same plug-in-unit ET16 can be used for both
symmetrical, coaxial and ANSI interfaces.
STM-1/OC-3 is the common interface at sites. In M14.0, the new
M98Amechanics enables integrating the STM-1/OC-3 interface. As
the integrated STM-1/OC-3 interfaces can be managed by the same
O&M interface, considerable savings can be achieved.
ETS2 is a new plug-in-unit for STM-1/OC-3 Terminal Multiplexer. It
has two STM-1/OC-3 optical interfaces and it frames, maps and
multiplexes 2x 64 2.048 Mbit/s tributaries into SDH STM-1 frame and
vice versa. In SONET OC-3 mode, ETS2 frames, maps and
multiplexes of 2x84 1.544 Mbit/s tributaries into SONET STS-3 frame
and vice versa. ETS2 supports MSP 1+1 protection for transmission.
All fibers are connected to the same plug-in-unit.
With the new optional 14CC TDM cabinet, STM-1 is available also for
the existing MSC Servers.
Type: Functional Unit with no sub-units

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
31
HLR AC EIR Architecture

Exchange Terminal- ET16 & ETS2

Function:The ET performs the


electrical synchronization
and adaptation of an
external TDM line. It is able
to do the HDB3/AMI/B8ZS
coding and decoding, insert
the alarm bits in the
outgoing direction, and
produce the PCM frame
structure.

ET16: provides 16 E1 interfaces


ETS2: provides 2 STM-1
interfaces

ETS2 & ET16 in GT4C-A


Redundancy: n
cartridge
ETS2 ET16

Fig. 23 ETS2 and ET16 in the GT4C-A cartridge

CN34014EN41GLN0
32 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.11 GSW 2KB - Group Switch 2KB


Purpose: The duplicated, 1024 PCM Bit Group Switch is the switching fabric of
the HLRi. The GSW2KB is housed in two identical SW10C-A
cartridges. It conveys the traffic passing through the HLRi and
switches the tones to the subscribers of the network element and to
the trunk circuits. It also establishes the needed connections to the
signaling units and the internal data transmission channels, and is
responsible for the sub multiplexing functions of the HLRi.
The GSWB2k is a scalable bit-based Group Switch system providing
capacity levels from 256 to 2048 PCMs in a single network element.
On hardware level, the GSWB2k concept is implemented as
SW256B plug-in unit. The maximum capacity is reached by using 8 x
SW256B plug-in units. The SW256B plug-in-unit can be used
simultaneously in the same cartridge with the existing SW128B plug-
in-unit.
Type: Subunit of the CMM

Group Switch 2KB (GSW2KB)

Function: The GSW2KB is the


switching fabric of the HLRi. It
conveys the traffic passing
through the HLRi and switches the
tones to the subscribers of the
network element and to the trunk
circuits. It also establishes the
needed connections to the
signalling units and the internal
data transmission channels, and is
responsible for the sub
multiplexing functions of the HLRi.

Redundancy: 2n

Fig. 24 GSW2KB in a SW10C-A cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
33
HLR AC EIR Architecture

4.12 HLRU - Home Location Register Unit


Redundancy: 2n, a maximum of 10 pairs of HLRUs
Purpose: The HLRU controls the home subscriber database (HOSTEL), which
is used for creating and modifying subscriber data. The HLRU is also
involved in call handling (HLR-inquiry).
Type: Computer Unit, with a dedicated storage device unit as a sub-unit.

Home Location Register Unit (HLRU)

Function:The HLRU controls the home subscriber database (HOSTEL), which


is used for creating and modifying subscriber data. The HLRU is also
involved in call handling (HLR-inquiry).

Redundancy: 2n

Fig. 25 HLRU in a MC2C-A cartridge

CN34014EN41GLN0
34 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

4.13 OMU - Operation and Maintenance Unit


Redundancy: 2n
Purpose: The OMU handles all centralized supervision, alarm and recovery
functions, and the connections towards the user interface (MMI-
System). The entire system software and the event buffer for
intermediate storing of alarms are stored in the OMU storage
devices.
Type: Computer Unit, with a dedicated storage device unit as a sub-unit.

Operation and Maintenance Unit (OMU)

Function:The OMU handles all


centralised supervision, alarm
and recovery functions, and the
connections towards the user
interface (MMI-System). The
entire system software and the
event buffer for intermediate
storing of alarms is stored in the
OMU storage devices.

Redundancy: 2n

Fig. 26 OMU in a DC3C-B cartridge

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
35
HLR AC EIR Architecture

4.14 STU - Statistical Unit


Redundancy: 2n
Purpose: The statistical unit collects performance and measurement data from
the network.
Type: Computer unit, with a storage device unit as a sub-unit

Statistical Unit (STU)

Function:The STU collects performance and measurement data from the


network.

Redundancy: 2n

Fig. 27 STU in a MC2C-A cartridge

CN34014EN41GLN0
36 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

5 Evolution towards Subscriber Data


Management (SDM) solution
The DX HLR offers a smooth and easy evolution path to the SDM solution. The DX
HLRe consists of the following elements:
• Front-End (FE) layer including the DX HLR and other applications
• Back-End (BE) layer including the One-NDS directory
• Value added features implementing multiple new functions to achieve more
benefits from the new architecture

Evolution steps of DX HLR


As the first step of evolution, the existing dataful DX HLR is connected to the One-
NDS to achieve multiple useful features. The usage of the HLR together with One-
NDS offers also additional capacity, because the HLR cleaning and pre-provisioning
features guarantee that the HLR stores only the data of active subscribers while the
inactive and pre-provisioned subscriber data is stored only in the One-NDS.
The second step of evolution provides you with multiapplication consolidation to
single repository. Subscribers can be provisioned to a multiaplication database over
the provisioning gateway that also takes care of data consistency between the HLR
and multi application subscriptions.

Subscriber Data Management (SDM) Solution

Fig. 28 SDM Solution

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
37
HLR AC EIR Architecture

CN34014EN41GLN0
38 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

6 HLR Innovation
Another evolution in the HLR products from NSN is the evolution from cabinet based
HLR (based on D900) towards the server based HLR Innovation (HLRi) which use
common platform called @vantage Platform. This server based HLRi have two types:
• Integrated HLRi (HLRi 1.0-2.6)
• Distributed HLRi (HLRi 3.0-ff)

HLR Product evolution


based on Platform Paradigm Shift

HLRc HLRi integrated HLRi distributed


HLRi1.0 – 2.6 HLRi 3.0 + ff
Telco Telco + IT Central Database + HLR application
proprietary monolithic distributed
Proprietary Telco 2-node cluster server with COTS for: High capacity central database for all
platform (EWSD) subscriber data
More price and cost transparency than
No price and cost with proprietary Hardware Distributed architecture
transparency
Higher performance due to performance Multi application support
Performance scaling with number of processors
scales with
processor speed
(central processor)
HLR Application
HLR Application
FSC HW
EWSD-
Oracle Database
Platform
Common Database
CCNC 1995-2007 SUN / FSC HW FSC HW
SSNC 2000-2012 2002 - 2012 2006-….
COTS – Commercial off the shelf

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
39
HLR AC EIR Architecture

Legacy Architecture
Several Subscriber Tables per Subscriber

Fig. 30 Legacy Architecture of HLRi

In HLRi the stored data can be in the format of MSISDN and its services or in SIP
address or the IP addresses depending on the applications or services available for
the subscribers.
The distributed HLRi can store up to 100 million subscribers’ data and for the
purpose of Authentication the AC Boxes will be inserted on the shelves of the HW.

CN34014EN41GLN0
40 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

HLR innovation distributed – The first in market commercial


available carrier grade implementation

HLRinnovation distributed Solution Description

HLR application HLR - Central network database


• Dataless HLR application • Carrier grade
• Open, standard interface towards database • Central database for all
subscriber and services
• Automated failover redundancy Application data
• Variable redundancy
Database
• All features inherited from previous HLRc and C-NTDB • Scalable up 100 Mio.
HLRi releases (EWSD based) Subscribers

Provisioning • Multi application database


• Open, standard interfaces towards database
provisioning • 3-site redundancy
• Streamlined subscriber provisioning process (automated
Provisioning resynchronization)
• Data validation, integrity checks
• Mass Provisioning USP Unique Selling Point
(30‘ subscribers / 8 hours) MML Man Machine Language

Fig. 31 Distributed HLRi can store up to 100 million subscribers

NSN Value proposition

HLRinnovation distributed Our Value Proposition

HLR -
• NSN HLR-Application
One Solution from one Supplier - SIemens
NSN Integration- and Migration-Support

• NSN Database Access Concept:


NSN OAM @vantage-Commander

independent scaling of HLR


Application
Application and Database
Database
C-NTDB

• Apertio Database

Provisioning
• NSN Provisioning Gateway

Fig. 32 NSN Value Proposition

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
41
HLR AC EIR Architecture

The idea behind common database is to avoid the redundant information of multiple
databases in the operator data. And additionally it gives Simplicity, Flexibility and
Efficiency in terms of single point of subscriber’s data provisioning.

Avoid Redundant Information of Multiple Databases


C-NTDB Directory Server to provide one Consistent Set of Data

•Type •Value
SDP clients •Type •Value
•MSISDN •Type •Value
HLR •MSISDN •0049308154711
•SIP-
•Location Area •0815@4711.com
Adr •Prepaid •No
HLR •Type •Value HSS
•Location
•041
Area
•MSISDN •4908154711 HSS EIR
•Terminal- •Name •Mike Miller
•Type •Value
ID •Home •http://www.universe.
AAA page gov
•Black •IPv4 •162.92.16.204
•IP-
•Grey •IPv6
•127.0.0.1 C-NTDB Address
•192.109.54.138
192.168.0.0/16 •SIP- •Sip:mike@universe.
EIR Directory Server Address gov.80
•SPID •0000.0c00.00c3.00-00
AAA
•Ack •No

One database
 for all network-centric subscriber information Simplicity
Easy extensible database
 ready for fast integration of new & 3rd party apps. Flexibility
Single point of subscriber data provisioning
 economies of scale and scope Efficiency

Fig. 33 Avoid Redundant of Multiple Database

CN34014EN41GLN0
42 © 2012 Nokia Siemens Networks
HLR AC EIR Architecture

HLRi with its clusters and installed AC Boxes are depicted in the figure 29 below:

HLRi 2.0 cluster


Typical configuration of one FSC PW 900 2-node cluster

Fig. 34 Examples of HLRi 2.0 Clusters

CN34014EN41GLN0
© 2012 Nokia Siemens Networks
43
HLR AC EIR Architecture

CN34014EN41GLN0
44 © 2012 Nokia Siemens Networks