Alcatel-Lucent - 8650 SDM R3.1 Product Description PDF

ALCATEL-LUCENT 8650 SDM SOLUTION
8650 SUBSCRIBER DATA MANAGER
PRODUCT DESCRIPTION
EDITION 3.1
8650 SDM - PRODUCT DESCRIPTION

Alcatel-Lucent – Subscriber Data Management
1/83
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization
TABLE OF CONTENTS
1 PREFACE.............................................................................................................................................6
2 INTRODUCTION.................................................................................................................................7
3 OVERVIEW .......................................................................................................................................10
3.1 MAIN MARKET CHALLENGES ............................................................................................................... 10
3.2 PRODUCT OVERVIEW .......................................................................................................................... 11
4 KEY BENEFITS OF THE ALCATEL-LUCENT 8650 SDM SOLUTION ....................................................12
5 PLATFORM ARCHITECTURE ..............................................................................................................17

5.1 COMPACT AND DISTRIBUTED CONFIGURATION ................................................................................ 17
5.2 COMMON COMPONENT TO COMPACT & DISTRIBUTED CONFIGURATION ...................................... 18
5.2.1 Hardware architecture ..................................................................................................................... 18
5.3 COMPACT CONFIGURATION.............................................................................................................. 20
5.4 DISTRIBUTED CONFIGURATION .......................................................................................................... 22
5.4.1 Hardware configuration for DB Nodes ............................................................................................. 24
5.4.2 Hardware Configuration For Front End Node ................................................................................... 25
6 SOFTWARE ARCHITECTURE & DEFENSE MECHANISMS ..................................................................26

6.1 SOFTWARE ARCHITECTURE.................................................................................................................. 26
6.2 LAYERED ARCHITECTURE ..................................................................................................................... 27
6.3 THE 8650 TELCO MIDDLEWARE........................................................................................................... 28
6.4 DEPENDABILITY OF A NETWORK ELEMENTS ........................................................................................ 28
6.4.1 Defense principles ........................................................................................................................... 28
6.4.2 Defense description ......................................................................................................................... 29
6.5 NETWORK LEVEL DEFENCE IN COMPACT CONFIGURATION .............................................................. 31
6.6 NETWORK LEVEL DEFENSE IN DISTRIBUTED CONFIGURATION ........................................................... 33
6.7 DEFENCE ............................................................................................................................................. 33
6.8 RESILIENCE .......................................................................................................................................... 34
7 SDM APPLICATION OVERVIEW DESCRIPTION .................................................................................35

7.1 INTRODUCTION .................................................................................................................................. 35
7.2 GSM/UMTS HLR APPLICATION OVERVIEW ........................................................................................... 35
7.3 IMS HSS APPLICATION OVERVIEW ....................................................................................................... 37
7.4 SUBSCRIPTION LOCATOR FUNCTION (SLF) OVERVIEW ....................................................................... 39
7.5 MNP APPLICATION OVERVIEW............................................................................................................. 40
7.6 EIR APPLICATION OVERVIEW................................................................................................................ 42

2/83
7.7 LTE APPLICATION................................................................................................................................. 43
7.8 OPEN DATA STORAGE APPLICATION................................................................................................... 44
8 SUBSCRIBER ADMINISTRATION .......................................................................................................46

8.1 SUBSCRIBER DATA MODEL................................................................................................................... 46
8.2 MANAGEMENT INTERFACES ................................................................................................................ 47
8.3 MASS MANAGEMENT........................................................................................................................... 47
9 INTERFACES AND PROTOCOLS .......................................................................................................48

9.1 PHYSICAL INTERFACES......................................................................................................................... 48
9.2 DESCRIPTION OF GSM/UMTS HLR INTERFACES................................................................................... 49
9.2.1 Interface between HLR and SMS-C (E interface) ................................................................................ 49
9.2.2 Interface between HLR and MSC/GMSC (C interface) ....................................................................... 49
9.2.3 Interface between HLR and VLR (D interface) .................................................................................... 49
9.2.4 Interface between HLR and SGSN (Gr interface) ............................................................................... 49
9.2.5 Interface between HLR and SCP (J interface) ..................................................................................... 50
9.2.6 Interface between HLR and GMLC (Lh interface) ............................................................................... 50
9.3 DESCRIPTION OF IMS-HSS & SLF INTERFACES ..................................................................................... 50
9.3.1 Interface between IMS-HSS and CSCF (Cx interface)......................................................................... 50
9.3.2 Interface between IMS-HSS and IMS-AS (SH interface) ...................................................................... 51
9.3.3 Interface between IMS-HSS and BSF (ZH interface) ........................................................................... 51
9.3.4 Interface between SLF and CSCF & IMS-AS (Dx interface) ................................................................. 51
9.3.5 Interface between IMS-HSS and 8670 GUP Server (Rp interface) ....................................................... 51
9.4 DESCRIPTION OF LTE INTERFACES ...................................................................................................... 52
9.4.1 Interface between 3GPP HSS and MME (S6a interface) ..................................................................... 52
9.4.2 Interface between 3GPP HSS and AAA (SWx interface) ...................................................................... 52
9.5 DESCRIPTION OF EIR INTERFACES ....................................................................................................... 52
9.5.1 Interface between EIR and MSC (F interface) and GGSN (Gf INterface) ............................................. 52
9.5.2 Interface between EIR and Central EIR (CEIR interface) ...................................................................... 53
9.6 DESCRIPTION OF MNP INTERFACES .................................................................................................... 53
9.6.1 Interface between MNP and HLR ...................................................................................................... 53
9.6.2 Interface between MNP and SMS-C.................................................................................................. 53
9.6.3 Interface between MNP and MSC/GMSC ......................................................................................... 53
9.7 INTERFACE BETWEEN 8650 SDM AND NETWORK MANAGEMENT....................................................... 54
9.8 INTERFACE BETWEEN 8650 SDM AND CCBS ....................................................................................... 54
10 OPERATION AND MAINTENANCE...................................................................................................55

10.1 MANAGEMENT ARCHITECTURE ........................................................................................................... 55
10.2 CENTRALISED OPERATION AND MANAGEMENT ................................................................................. 55
10.3 8650 SDM MANAGEMENT FUNCTION ................................................................................................ 56
10.3.1 platform management ..................................................................................................................... 56
11 ATCA PERFORMANCE ......................................................................................................................59

11.1 GSM/UMTS HLR CAPACITY .................................................................................................................. 59
11.1.1 System dimensioning DATA.............................................................................................................. 59

3/83
11.1.2 HLR/AuC capacities ......................................................................................................................... 60
11.2 IMS-HSS CAPACITY .............................................................................................................................. 61
11.3 EIR CAPACITY....................................................................................................................................... 62
11.4 MNP CAPACITY .................................................................................................................................... 62
11.5 PROVISIONING CAPACITY ................................................................................................................... 63
11.6 8650 SDM SN7 CONNECTIVITY .......................................................................................................... 63
12 ATCA V2 TECHNICAL CHARACTERISTICS ........................................................................................65

12.1 PHYSICAL DIMENSIONS....................................................................................................................... 65
12.2 SPACE REQUIREMENTS ........................................................................................................................ 65
12.3 CONSUMPTION .................................................................................................................................. 66
12.4 ENVIRONMENTAL CONDITIONS ......................................................................................................... 66
12.5 POWER SUPPLIES AND CABLING ......................................................................................................... 67
12.5.1 Lighting and power outlets ............................................................................................................... 67
12.5.2 Power requirements and security ...................................................................................................... 68
12.5.3 Cabling ........................................................................................................................................... 69
12.5.4 Grounding requirements.................................................................................................................. 69
12.5.5 Power generators............................................................................................................................. 70
13 ATCA V1 TECHNICAL CHARACTERISTICS ........................................................................................71

13.1 PHYSICAL DIMENSIONS....................................................................................................................... 71
13.2 SPACE REQUIREMENTS ........................................................................................................................ 71
13.3 CONSUMPTION .................................................................................................................................. 72
13.4 ENVIRONMENTAL CONDITIONS ......................................................................................................... 72
13.5 POWER SUPPLIES AND CABLING ......................................................................................................... 73
13.5.1 Lighting and power outlets ............................................................................................................... 73
13.5.2 Power requirements and security ...................................................................................................... 74
13.5.3 Cabling ........................................................................................................................................... 75
13.5.4 Grounding requirements.................................................................................................................. 75
13.5.5 Power generators............................................................................................................................. 76
GLOSSARY ..............................................................................................................................................77

4/83
LIST OF TABLES
Table 1: Common parameter values for the HLR/AuC.................................................................60

Table 2: HLR/AuC profile...........................................................................................................60
Table 3: HLR/AuC capacity (KMS = Kilo Mobile Subscribers) .......................................................61
Table 4: IM-HSS profile .............................................................................................................61
Table 5: IM-HSS capacity (KMS = Kilo Mobile Subscribers) ..........................................................62
Table 6: EIR capacity (MS = Million Mobile Subscribers) ..............................................................62
Table 7: MNP capacity (MS = Million Mobile Subscribers) ...........................................................63
Table 7: Provisioning Capability.................................................................................................63
Table 9: SS7 connectivity ...........................................................................................................64
Table 10: Environmental conditions compliance..........................................................................67
Table 11: Environmental conditions compliance..........................................................................73

5/83
1 PREFACE
This document described the 8650 Subscriber Data Manager (SDM) product.
The Alcatel-Lucent 8650 SDM product is included in the following Alcatel-Lucent solutions:
2G/3G Core Network solution with HLR Application
IMS solution with IMS HSS application
LTE Solution with LTE application (3GPP HSS).
The Alcatel-Lucent 8650 SDM product can also be used to store subscriber’s data for any customer
or third party application providing a simple solution for network data storage.
Together with introduction of a new generation of Hardware platform, the 8650 SDM solution is
available with key applications such as GSM/UMTS HLR, IMS HSS, MNP, EIR, Open Data Storage
applications. The first generation of hardware product of the SDM portfolio (i.e 1430) with large
installed base can smoothly evolve to 8650 SDM by a software upgrade.
Please refer to Alcatel-Lucent roadmap for details on availability of applications and associated fea-
ture set.
Alcatel-Lucent would like to inform his customer that information presented in this document is
subject to change without notice.

6/83
2 INTRODUCTION
The Alcatel-Lucent 8650 SDM solution comes with a set of Database applications, key components
in their respective network infrastructure. This includes:
GSM/UMTS HLR application, highly reliable and field-proven unit, needed to support 2G or 3G
subscribers for circuit-switched and packet-switched domain. According to the 3GPP standards,
the Home Location Register (HLR) is the database for a given user containing information related
to subscriptions for the use of 2G and 3G mobile networks in circuit/packet-switched domain.
IMS HSS application that supports IP multimedia users as defined by 3GPP’s IP multimedia
Subsystem (IMS framework). Alcatel-Lucent 8650 SDM can also manage IMS subscribers
connected to fixed networks according to TISPAN ensuring full Fixed Mobile Convergence
support.
MNP application that supports mobile number portability as a relay function (MNP-SRF)
managing and re-routing call and non call related messages to appropriate portability domain.
EIR application that supports the competitive advantage to control the fraudulent usage of stolen
or prohibited terminals.
LTE 3GPP HSS application that supports management of subscribers on new Enhanced Packet
Core infrastructure.
Open Data Storage that can be used as a mechanism for applications to store subscriber data
and application specific data that requires high availability. This mechanism is provided as a
complementary mechanism to the Sh interface supported with the IMS HSS application.
The 8650 SDM can be deployed in a network in any configuration matching customer expectation:
Either standalone application like HLR/AuC only, IMS HSS only,...
Or a mix of any applications available on the Alcatel-Lucent 8650 SDM portfolio.
In case of implementation of single application, it is important to note that smooth evolution from
single to multiple applications can be easily performed. For example, the Alcatel-Lucent 8650 SDM
evolution from HLR deployment to combined HLR/IMS HSS deployment will be performed by release
upgrade or application activation depending on the situation while using the hardware already de-
ployed for the HLR application.
The Alcatel-Lucent 8650 SDM can be deployed in 2 network configurations:

The “Compact configuration” where the applications and subscriber database are integrated on
the same physical Network Element. This configuration is very efficient for small and medium
size network (Ex: up to 6 millions GSM/UMTS HLR subscribers).
Geography redundancy is offered in compact configurations with mated pair.
The “Distributed configuration” where the applications run on a dedicated Network Element
(called “Front End”) and the Subscriber Database runs on another Network Element (called
“Database node”). All these nodes can be either collocated in the same site or located in a

7/83
different remote site. This architecture is especially efficient for large network. With this
architecture, application and database can scale and evolve independently and capacity is
virtually unlimited (ex: up to 60 Million subscribers). Two or even three level of geographical
redundancy for the database can be offered in this configuration.
The following figure shows the “Compact” architecture at the heart of these networks and subsys-
tems, and it shows where they overlap and interact.
UNC
VoIP GMSC
Public
TDM/ATM Switched
Backbone Network
C,D
Wm Wm’
WiMAX SDM SIP

RAN AS
MSC
CSCF
A C,D Cx,Dx,Sh
Gb IuCS
Gr/S6a
Gc
GPRS IP Packet Data

Backbone
IuPS Network
SGSN GGSN
/MME
Figure 1. Network architecture with Compact architecture

8/83
Following figure shows the “Distributed” architecture at the heart of these networks and subsystems,
and it shows where they overlap and interact.
UNC GMSC
VoIP
Public
TDM/ATM Switched
Backbone Network
C,D
Wm’
Wm
Front
Front
End
MSC End Front
A End SIP
AS
C,D
IP Cx,Dx,Sh CSCF
IMS
Gb
Database Network
Database
IuCS Gr/S6a
Gc
GPRS IP Packet Data
Backbone
IuPS Network
SGSN GGSN
/MME
Figure 2. Network architecture with Distributed configuration

9/83
3 OVERVIEW
3.1 MAIN MARKET CHALLENGES
To compete more effectively, capture and grow market share, all service providers need the ability to
go beyond offering bundled services. They must now provide personalized, blended services that
span across individual types of access methods and devices. To do this, service providers need to
make their networks more agile. A key element to facilitating network agility and strategically posi-
tioning a service operation to have the flexibility to shift business paradigms is to maintain simplifica-
tion with a subscriber centric approach.
Before establishing network agility, service providers must deal with consolidation and optimisation
of their traditional install Base. The growth in subscribers and services has lead to growing complex-
ity of today’s wireless networks. Operators are now facing massive networks with multiple database
(like HLRs) to manage, leading to high ongoing capital expenditures and operating costs.
As the repository of all subscribers’ information, the 8650 SDM is the knowledge center in multi-
access networks fixed and mobile. It consequently plays a central and pre-eminent role providing a
lay sound foundation to a subscriber centric view with clear reduction in operational cost by support-
ing the following key requirements:
High
High Performances
Performances High
High Flexibility
Flexibility
• Capacity (virtually unlimited) • Provisioning

• Compactness • Unified Data Management
• Scalability • Connectivity (sig. & OAM)
• Mass administration/provisioning • Multi-application system 3G, IMS, …
• Fast addition of new features • Ability to separate DB from appli
High
High Reliability
Reliability Openness
Openness
• Data availability and security • Open system/platform

• High level of redundancy • Open database
• Powerful O&M (IT Based) • Open interfaces
Alcatel-Lucent’s 8650 SDM Solution provides a unique business value to service providers by sup-
porting short term rationalisation and longer terms objective of new service introduction and agility
to achieve rapid adaptation to new market needs.

10/83
3.2 PRODUCT OVERVIEW
Alcatel-Lucent 8650 SDM solution takes benefits of the product of the last generation:
One open and standard platform based on the latest IT technology (ATCA) and on
commercial off-the shelf database (carrier grade MySQL)
A flexible ”independent application” platform: Provide a database server platform to
support Multi-application: HLR, IMS HSS, LTE, Open Data Storage Application (LDAP server),
Mobile Number Portability Database, Equipment Identity Register.
High flexibility in network design with compact and distributed configuration
High capacity in a reduced footprint
Data integrity
Flexible & highly efficient provisioning with Unified Data management to support a
subscriber centric view
Support wide range of protocols for provisioning and external application interaction
High degree of availability
Flexible redundancy schemes
IP Connectivity (management and signaling with SIGTRAN capabilities)
High speed links
Standard and open interfaces (IP, SOAP, Corba)
IT based O&M
Future proof solution (2G/3G capable, IMS capable, and ready to LTE)

11/83
4 KEY BENEFITS OF THE ALCATEL-LUCENT 8650 SDM SOLUTION
One open and standard IT platform

Based on the latest generation of platform and technologies (benefit from ATCA standard,
Carrier Grade MySQL, Linux Rehat, …)
Focus on value added applications
Open and highly flexible interfaces : LDAP, SOAP
High scalability and reliability
Significantly reduced time to market for new service introduction (significant development
efficiencies)
High capacity & scalability in small footprint

8650 SDM solution ranges from 200K to 60 Million Subscriber capacity:
Solution with a single rack (with compact configuration),
Solution with very high capacity (with distributed configuration),
Smooth evolution from compact to distributed configuration
A small footprint cabinet (19"),
And minimized power consumption.
Alcatel-Lucent solution based flexible platform:

Alcatel-Lucent has defined flexible platform able to support Multi-applications such as:
GSM/UMTS HLR application,
IMS HSS application,
LTE application
SLF
Mobile Number Portability Database (MNP-SRF)
Equipment Identity Register (EIR)
Open Data Storage Server
The Alcatel-Lucent flexible platform supports also multi-protocols in order to support all these appli-
cations: MAP, DHCP, RADIUS, DIAMETER, LDAP.
The 8650 SDM database framework architecture allows support of Unified Data profile for the over-
all application portfolio as well as integration of specific profiles for 3rd party applications.
Highly flexible & efficient provisioning

High performance and flexibility for provisioning using standard interfaces on IP

12/83
SS7 flexibility
SN7 routing
IP signaling (SIGTRAN)
HSL (2 Mb)
Compliance
Compliance to 3GPP Rel5, Rel6 and partly Rel7 specifications and compliance to TISPAN R1 and
partly R2 specifications.
Convergence
Convergence between fixed and mobile networks through a common data model based on
3GPP user data model
Interoperability
Full interoperability with most major core network equipment vendors.
Proven field’s interoperability within others vendors in GSM/UMTS, GPRS, and WIMAX networks.
Interoperability with Third Party S-CSCF, I-CSCF and AS
Active participation of Alcatel-Lucent in NV IOT forum.
Active participation of Alcatel-Lucent in WIMAX IOT forum
Field proven solution

More than 600 HLR/AuC including legacy HLR serving more than 300 Million Mobile
Subscribers.
More than 170 implementations of SDM solution in use.
High reliability
Thanks to robust hardware platform and sophisticated software defense mechanisms, Alcatel-Lucent
8650 SDM solution can offer 99.9999 % availability including hardware and software failures by
support of local and geographical redundancy.
8650 SDM solution provides flexible redundancy schemes with local/geographical redundancy
models, in real time mated-pair or N+K redundancy (distributed configuration) , with automatic
switchover in case of disaster.
8650 SDM solution also integrates overload control mechanism to ensure and protect system avail-
ability and capacity to resume to normal handing in a very efficient manner.
8650 SDM solution integrates a 3 sites redundancy in Active/Stand-by/Stand-by mode in order to
have at any time 3 copies of Databases in different geographical locations.

13/83
Operation and Maintenance
Rich portfolio of O&M features based on state-of art OAM&IP (IP, CORBA, SOAP, Web based GUI).
Solution is also integrated with Alcatel-Lucent Cross-Domain Maintenance Center (1300 XMC) solu-
tion, that provides support for remote operation and maintenance.
Opened management interfaces
Alcatel-Lucent 8650 SDM provides opened IP based interfaces with Corba, HTML protocols, XML
protocols and SOAP.
Mass management capabilities
Mass management gives to operator the ability to activate mass operations like database popula-
tion, database modification, database extraction through xml files over https.
Feature rich
Following are the main features proposed in HLR application:
3GPP R5/R6 ready for 2G /3G subscribers
GPRS handling: managed on a subscribers basis.

Multi PLMN handling: to manage several PLMN in the same country for 2G /3G subscribers.
Multi country handling: to manage several Countries in the same SDM.
Mobile Number Portability: can manage MSISDNs from different national PLMNs, and as
consequence with different NDC
CAMEL phase 1, phase 2, phase 3, phase 4 with:
standardized solution for Prepaid Short Message Service Mobile Originating, including in
roaming situation
service triggering on mobility events for Mobility Management,
service triggering when unsuccessful call establishment occurs,
ATSI, ATMO.
VT, D-CSI triggers
SMS-MT CSI trigger
Location Based Services: pre LCS Feature with ATI, automatic Location retrieval, as well as
standard LCS.
Short Message Services: delivery of SMS as well as Filtering of SMS on operator basis to prevent
operator’s network from SMS of non-cooperant network
Extended services such as :
Automatic Device detection
MAP screening feature for advanced routing scenario
MVNO features
Management of IMSI Signalling without using MSISDN

Management of shared M2M subscription: one M2M subscription shared with unlimited
number of IMSI

14/83
Routing of SMS via the HPLMN
Notification of subscribers data change based on Camel.
Following are the main features proposed in HSS application:

Full Cx Compliance (UAR/A, SAR/A, LIR/A, MAR/A, RTR/A, PPR/A)
Full Sh Compliance (UDR/A, PUR/A, SNR/A, PNR/A)
Support for Zh Interface
Support for full SWx interface
Multiple MSISDN
SiFC (Shared Initial Filter Criteria, iFC) support
(Wildcard PUID (ALU Proprietary)

Early IMS Security -Secure IP address binding with PRID/PUID (in HSS DB)
Public Service Identity (PSI)
Application Servers' Support including Transparent Data (Aliases Repository Data)
Unregistered Originating IFC support
3GPP R7 Sh (SNA) Efficiency Enhancement
HSS Support for Default PUID per 3GPP 23.008 CR 147
Phase-1 SLF with Redirection (Stand-alone mode for networks with multiple SDM HSS systems)
MAP interface to external AuC for user AKA authentication
MAP interface to external HLR for user geo-location, status
Sh Location information and Mobile user status (GSM/ UMTS)
PRSET for Bulk Registration Access GW support
Nass Bundled authentication scheme as defined in ETSI TS 183 033
Packet cable (Cablelabs specs) support DisplayName & 3GPP R7 SIP Digest Auth. (per TS
23.008, TS 29.109, TS 29.228 &229)
Following are the main features proposed in EIR application:

Check IMEI
Black list management
Grey list management
White list management
IMEI Duplicated list management
IMSI override list management
EIR Delta list management
CEIR interface management
EIR Capacity
EIR list provisioning (individual or by ranges)

15/83
IMSI override list provisioning
SS7 management for EIR application
log management for EIR application
Support of S13 interface to the SGSN
Following are the main features proposed in MNP application:

SS7 interoperability regarding others vendors (considering they are compliant to standards)
3GPP TS 23.066 - ETSI MNP-SRF solution
Voice call
SMS routing
Support of Optimal Routing
Support of Any Time Subscriber Interrogation - ATSI
Support direct routing
Support indirect routing
Support indirect routing with reference to the subscription network
Generation of CDR for re-routed messages
Complete party number: All the digits of the called number are analysed
Partial party number: Only the first digits of the called number are analysed
Routing Number: Routing number set before the Directory Number

MNP Translator Data (MNP Translator Management)
Following are the main features proposed in LTE application:

Full S6a Compliance (AIR/A, ULR/A, NOR/A, CLR/A, IDR/A, DSR/A, PUR/A, RSR/A) towards
MME
Full SWx Compliance (MAR/A, SAR/A, PPR/A, RTR/A) towards AAA
Roaming between 2G/3G accesses and 4G access
Provisioning of 2G/3G/4G subscriber in one command
Combined HLR/HSS/LTE support
Provisioning (Corbal & SOAP)
Manual De-registration via provisioning interface
MVNO support
SCTP over diameter support
SLF support for LTE
Support of Lawful interception interfaces, including CALEA interfaces

16/83
5 PLATFORM ARCHITECTURE
5.1 COMPACT AND DISTRIBUTED CONFIGURATION
Alcatel-Lucent 8650 SDM product is designed on top on a very flexible platform. With this platform,
applications can be deployed in 2 different configurations: compact and distributed.
The distributed configuration is perfectly adapted for large network (more than a few millions
subscribers) as it provides the following benefits:
Capital expenditure optimization thanks to independent dimensioning for both Database nodes
and application Front Ends
Simplified network configuration thanks to the virtualization concept. As the database node is
accessed from any front-End node and the Front End application nodes are used in a load
sharing mode, the network does not need to manage any kind of routing, such as with legacy
HLR with IMSI or MS-ISDN routing information.
Simplify the provisioning system requirement thanks to an integrated provisioning application
managing virtualization over subscriber data location. With a unique database repository, the
subscriber location is completely handled by the Alcatel-Lucent 8650 SDM solution. Furthermore
thanks to advanced protocol Corba, SOAP or XML, it is possible to greatly simplify and optimize
the interface with the provisioning system.
Greater scalability with access to unlimited capacity.
Greater flexibility for new application introduction.
Simplified operation with common management solution for all nodes.
In the Alcatel-Lucent solution, the Alcatel-Lucent 8650 compact configuration is an optimised way
to implement Subscriber Data Management Solution for small and medium size network. It is also a
perfect solution for networks where IP backbone does not provide the level of quality of service re-
quired by a distributed database application. This configuration provides:
Optimized capital expenditure and footprint for small and medium size network with a solution
within a single rack (or 2 racks for geographical redundancy)
Simplified daily operation thanks to a solution in a single node (simple software upgrade, simple
backup/restore, simple Network operation)
In the compact configuration, the hardware and software architecture is exactly the same as in a
distributed configuration with a clear separation of Database from the application. This solution pro-
vides also the same functional level as the distributed architecture (including the real time geo-
graphical redundancy with the mated pair functionality of the database). The 8650 SDM compact
solution is available with both 1st and 2nd generation of ATCA board technology (ATCA V1 and
ATCA V2).
Alcatel-Lucent is perfectly aware that the network can grow up to a size where a distributed architec-
ture can be more efficient than the compact configuration. Thus, an upgrade procedure can easily
transform the compact solution in a fully distributed application by adding a redundant database
and by reusing the exiting hardware as front end.

17/83
The following table compares the advantage of each configuration:
Compact Configuration Distributed Configuration

Possibility of multiple integrated Possibility of multiple distributed
applications applications
Cost effective solution for small network Cost effective solution for large network
Possibility to share data between multiple Possibility to share data between multiple
Alcatel-Lucent applications Alcatel-Lucent and external applications
Optimal response time Virtual concept (Unique Subscriber
Minimum requirement on WAN quality of Database in the network)
service Front End Nodes in load sharing mode
Simplified software upgrade for small Independency of dimensioning of Front End
network Nodes and Database Nodes
No Capacity limitation
5.2 COMMON COMPONENT TO COMPACT & DISTRIBUTED CONFIGURATION
5.2.1 HARDWARE ARCHITECTURE
Alcatel-Lucent has built a carrier grade platform composed of standard IT boards from the em-
bedded market to offer the life cycle expected by the Alcatel-Lucent customers: production time,
maintenance and support from 5 to 10 years period.
This platform ensures:
Service continuity
Baseline for evolution,
Flexibility
Real-time performance
Cost effective development
Hardware/software independency
This platform is a high available distributed platform composed of blades or stations (names given
to boards which are plugged in a middle plane) compliant with the Advanced Telecom Computing
Architecture (ATCA) open standard. These stations are interconnected by a secured Local Sub-
Network (LSN). This LSN is based on Ethernet technology (1Gbit/s).
These stations can basically support four types of functions:
Control function
Processing function
Database function
Signaling function
It is possible to combine Processing and Signaling some of these functions on a same station.
Main hardware components of Alcatel-Lucent 8650 SDM are:

18/83
19” rack with its power supply distribution and alarm board
ATCA sub racks (1 or 2) including FAN, shelf management, power supply modules.
Ethernet Switches: includes a base switch with 12 internal Gigabits/sec Ethernet ports. Four
Gigabits/sec Ethernet uplinks and one-10Gigabits/sec Ethernet uplinks are supported for ATCA
V2. Eight Gigabits/sec Ethernet uplinks are supported in ATCA V1. Two Ethernet switches are
embedded in each ATCA sub racks in active/active redundancy mode.
Control stations: two Control stations operate in duplex (active/hot standby redundancy mode)
and support platform administration & control and operation & maintenance management. Each
Control station is equipped with 2 AMC (Mezzanine Card) disks for ATCA V2 and with 2 PMC
disks for ATCA V1.
Database stations: several database stations operate by pair. Scalability of the solution is
achieved by adding of database stations by pair in the platform. Each pair of database station
handles the same replicated fragment of subscriber’s data. Both stations of the pair operate in
active/active mode for read operations and in an active/standby mode for write operations. Each
DB station is equipped with 2 AMC (Mezzanine Card) disks and with 2 PMC disks for ATCA V1.
Real time stations: several real time stations operate in N+1 load sharing redundancy mode.
These stations support the real time processing function and signaling applications. Each RT
station is equipped with one SS7 AMC (Mezzanine Card) with 4 E1/T1 for TDM connection in
ATCA V2, and in ATCA V1 with one SS7 PMC with 2 EI/T1.
2 redundant routers in charge to connect the platform to an IP network (local LAN, local
management, remote OS, other NE, …). These routers which can either be provided by Alcatel-
Lucent or the ones of the customer (standard features available with most of the routers of the
market are required) are connected directly to the dual Gigabits Ethernet network using the
uplinks of the Ethernet switches. In provided configuration 14 auto-sensing Gigabits Ethernet
ports are available for external connections. Four ports can be equipped with optional modules
to support optical connectivity.
Figure 3. ATCA Rack
Each station (based on ATCA technology of 2nd Generation) is composed of:

19/83
64 bits Dual Core Processor of the latest generation with its associated chipset and memory (8
Gbyte)
Linux operating system
2 Gb Ethernet ports to get to the Inter-Station LAN through the redundant switched Ethernet LAN
AMC Module (for E1/T1 connection) for Real Time Boards when SS7 connectivity is required.
AMC module with disk for Database station and Control Station
Figure 4. ATCA V2 Control Station
Each station (based on ATCA technology of 1st Generation) is composed of:

32 bits Pentium 1.8 Ghz M Processor with 4Gbyte Memory Board
Linux operating system
2 Gb Ethernet ports to get to the Inter-Station LAN through the redundant switched Ethernet LAN
PMC Module (for E1/T1 connection) for Real Time Boards when SS7 connectivity is required.
PMC module with disk for Database station and Control Station
5.3 COMPACT CONFIGURATION
Three pre-defined compact configurations are available:

Small configuration: minimal hardware configuration
Medium configuration: one sub rack fully equipped
Large1 configuration: 2 sub rack fully equipped
1 Large configuration only supported with ATCAV1 Hardware

20/83
Control station
DB Station
RT station
Ethernet Switch
FAN
Ethernet Switch
Control station
DB Station

Configuration
Small compact
Figure 5.
RT station
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Control station
DB Station
DB Station
RT station
RT station
RT station
Ethernet Switch
FAN
Ethernet Switch
Control station
DB Station
DB Station
RT station
Configuration
RT station
Medium compact
RT station
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Control station DB station

DB Station DB Station
RT station RT station
Ethernet Switch Ethernet Switch
Standard compact configurations
FAN
FAN
Ethernet Switch Ethernet Switch

Control station DB station
RT station
Configuration
RT station
Large compact
RT station
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1 2 3 4 5 6 7 8 9 10 11 12 13 14
RT station
21/83
5.4 DISTRIBUTED CONFIGURATION
For large networks (over a few millions of subscribers), Alcatel-Lucent proposes the 8650 SDM dis-
tributed configuration:
The Alcatel-Lucent 8650 SDM distributed configuration is a natural evolution of compact configura-
tion, taking advantage of a clear separation between applications and Database functions distrib-
uted over several stations.
The Alcatel-Lucent distributed 8650 SDM is built with:
Data repository servers (Network Database Node) with disk persistence and full in-memory
database for real-time access that securely stores user profiles over different physical locations.
Application Front Ends handling the traffic from the Network. The Front End is “Data less”
and retrieves all application’s data in the Network Database node. This architecture provides
high flexibility in network design and organization as a Mobile or Fixed network element,
Customer Care & billing system, third party applications can access any Front End to get SDM
services.
Distributed Configuration
OSS/ BSS / NM
Corba/
CorbaXML
Data Data Database

repository repository Back-end
Nodes
IP
Data Network Data
repository repository
Real-time
HLR /Provisioning HSS/Provisioning AAA/Provi sioning Multi Front-end
application application application application Nodes
Diameter, Radius, MAP, CAP, DNS, LDAP, SMPP, ...
Mobile & Fixed networks (CS&PS, IMS, TISPAN, WLAN, WIMAX RAN, UMAN...)
IMS 2G/3G/ UMA/

GSM/CDMA WLAN
Figure 6. 8650 SDM distributed architecture

22/83
The Alcatel-Lucent distributed 8650 SDM is designed to:
Handle subscriber data in high available architecture with database supporting local and remote
redundancy in 2 sites or 3 sites providing up to 6 copies of the subscriber information.
Handle high level of redundancy on applications with support of Front End redundancy. All
processing boards inside a Front End are working in load-sharing mode allowing an n+k
redundancy. Furthermore, at network level, all Front Ends can also be configured to work in load
sharing mode. This allows much flexibility in term of network design to optimize both network
element numbers and transmission capability.
Provide flexible configurations:
Specialized Front End (Mono-application). This configuration allows limiting the risk of new
technology in a live network.
Multi-applications Front End. This configuration allows optimizing number of physical
elements in the network thus reducing operation expenses.
Insure the best scalability: capacity extension can be handled in a very efficient and simple way
by either adding Database node to increase storage capacity or by adding Front End node to
match traffic growth.
Adding a database node does not impact End user service. Subscribers can be easily
migrated from existing Database to new database to share the load on the new system. But
it is also possible to avoid this migration by configuring the 8650 SDM to create all new
subscribers on the newly installed equipments.
Adding a Front End node is performed without impact either on Database node or on other
existing Front End.
Insure data coherency:
Insure ACID properties (Atomicity, Consistency, Isolation, Durability) of database update at
network level
Insure coherent backup/restore at database node level. All the data concerning a
subscriber are stored in a same database node. In addition, subscriber data are never
duplicated except on the peer database for geographical redundancy reason.
Insure simple and efficient network upgrades:
Network upgrades can be tested on a part of the network before generalization.
Network upgrades do not impact subscriber’s services.
All network elements can be remotely upgrades.
Insure flexible control of subscribers’ data on the distributed database. Alcatel-Lucent 8650 SDM
allow automatic and/or manual repartition of data subscribers among different database nodes.
With automatic mechanisms, it is possible to design flexile algorithm for example based on
database load or on specific subscribers attributes like zip code …
Insure efficient provisioning solution. The strength of Alcatel-Lucent provisioning solution can be
summarized as follow:
Support of unique database repository. Any modification of this data repository is
instantaneously visible to the network.
Support of distributed provisioning point. Each Front End node can be used as a
provisioning point. This allows Customer Care & Billing system or third party application to
secure the connection to the database by load sharing mechanisms on the nearest Front
Ends.

23/83
High performance of provisioning (capacity to reach Million operations per hour with
multiple Front Ends).
Data coherency control before any modification to the database.
Support of advanced protocol like Corba, XML or SOAP.
Furthermore, initialization of a Front End will not impact IP network engineering rules, as the
Front End does not need to download all subscribers’ data in a memory cache. Data subscriber
information is retrieved from the database at transaction level when a new request is handled by
a Front End application.
5.4.1 HARDWARE CONFIGURATION FOR DB NODES
As distributed configuration is designed for large networks, only 2 pre-defined configurations are
available for Database Node (only released with ATCA V2 Hardware):
Medium configuration: one sub rack fully equipped
Dual configuration: 2 sub rack fully equipped
Medium Dual
configuration configuration
FAN
1 2 3 4 5 6 7 8 9 10 11 12 1314
Ethernet Switch
Ethernet Switch
Control station
Control station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
FAN FAN
1 2 3 4 5 6 7 8 9 1011 12 13 14 1 2 3 4 5 6 7 8 9 1011 12 13 14
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Switch
Control station
Control station
Control station
Control station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
DB station
Figure 7. Database Node standard configuration

24/83
5.4.2 HARDWARE CONFIGURATION FOR FRONT END NODE
Front End hardware is based on a medium configuration (only released with ATCA V2 Hardware). It
is possible to optimise footprint with 2 FEs within a single rack.
Figure 8. Front End Standard configurations

25/83
6 SOFTWARE ARCHITECTURE & DEFENSE MECHANISMS
6.1 SOFTWARE ARCHITECTURE
8650 SDM applications are based on a multi-station (distributed) multi-schema and multi-
applications architecture.
Multi-station architecture is composed of:
Control station, in charge of platform management, in 2N redundancy,
Real time stations in charge of real time requests processing and network signaling in N+K
redundancy,
Database stations in charge of database management and DB access requests (from real-time
or provisioning, in 2N redundancy.
Control stations Config OAM Config OAM

Pilots active standby
active/standby DBMS DEFENCE DBMS DEFENCE
GENERIC SERVICES GENERIC SERVICES
MS A MS A MS B MS B
DB stations
2N active DBMS DBMS DBMS DBMS
APPS
HLR-RT APPS
HLR-RT APPS
HLR-RT
TCAP TCAP TCAP

RT stations SCCP SCCP SCCP
MTP3/M3UA MTP3/M3UA MTP3/M3UA
N+1 load sharing
Level 2 Level 2 Level 2
Level 1 Level 1 Level 1
Figure 9. 8650 SDM software architecture
It is important to note that software architecture is exactly the same for compact and distributed ar-
chitecture of 8650 SDM. In case of distributed architecture, the DB stations are connected to the Real
Time station through a WAN instead of the local Ethernet switch.

26/83
6.2 LAYERED ARCHITECTURE
Alcatel-Lucent solution key architecture principle is a layered architecture offering a clear separation
between application functionality and database infrastructure where the subscriber information is
physically located.
Client Client Client
Protocol handlers
(SS7, Diameter, LDAP)
Front End NE
Applications
Partitioning Layer
Database NE
Database
Database
Figure 10. 8650 SDM Layered Architecture
The Application Layer with its protocol handlers contains a number of applications (e. g. HLR,
HSS application), each supporting the access protocols (e. g. MAP, Diameter etc.) required by the
application. Applications are handling and relying on partitioning layer to access Service or Sub-
scriber related data. Application can be built independently from the physical organization of the
data. Application covers:
GSM/UMTS HLR application real-time processing

IMS HSS application real-time processing
SLF application real-time processing
LTE application real-time processing
MNP application real-time processing
EIR application real-time processing
Open Data Storage real-time processing

27/83
The Partitioning Layer supports:
Management of connections to the database infrastructure on behalf of the applications
Manages transactions and ACID properties of accesses to the underline database

infrastructure.
Manages connection and failover to ensure connectivity to the active nodes
Provides abstraction for the application when managing to manage local read access.
Provides management of data to be cached
Mapping to the underlying data format (e.g. relational tables or hierarchical objects)
Routing function (index server) to allow application to be managed independently from the
physical location of the data.
The Database Layer holds the data without understanding its specific meaning. Database infra-
structure supports and manages geographical redundancy (Two or 3 sites redundancy) with replica-
tion mechanisms. It also ensures and manages database transactions (i.e. commit or cancel). The
database Layer integrates an in-memory database to guaranty best in class response and perform-
ance for the applications of the 8650 portfolio.
6.3 THE 8650 TELCO MIDDLEWARE
Alcatel-Lucent ATCA platform is a consistent set of software services and hardware configurations
based on standard / bought off-the-self elements whenever relevant.
The hardware is based on third-party UNIX/LINUX Information Technology (IT) platforms providing
a secure carrier-class system.
The 8650 Telco middleware provides some of the infrastructure services needed by server applica-
tions. It supports applications in providing multi-client, multi database and multi-threaded interfaces.
This generic architecture framework offers generic services: such as authentication and access con-
trol, logging, alarming, provisioning interfaces, defense, online version change, high performance.
6.4 DEPENDABILITY OF A NETWORK ELEMENTS
This section describes the 8650 SDM defence principles at the Application level for a single network
element: Compact node, Database node or Front End node.
6.4.1 DEFENSE PRINCIPLES
The 8650 SDM defense is based on the following principles:

Redundancy of hardware and software components,
Organization of an automatic defense system for:

• Detecting hardware and software faults,
• Isolating defective elements,

28/83
• Reconfiguring 8650 applications elements.
6.4.2 DEFENSE DESCRIPTION
The defense is split in several functions:

Fault detection and notification
• HW and SW faults,
• Mechanisms to trace and notify events or alarms.
Confinement
• Shutdown of the element in fault,
• Notification of the fault in the system.
Recovery
• Re-allocation of the tasks of the element in fault to another entity.
Maintenance
• Fault localization and identification including DUMP processes,
• Repair process in case of HW outage,
• Station restart including the application level.
The defense granularity is the station (control, DB station or RT station).

Each software module embeds a local defense function able to request a defense action in associa-
tion with the Core Middleware.
The local defense function is in charge of:
Faults management,
The detection of faults in association with the application,
The filtering, evaluation of fault severity,
The actions related to the defense process (Shutdown,..)
Generation of corresponding alarms to the alarm service,
Generation of events to the log service,
Application watchdog supervision,
Detection of application misbehavior (i.e. loop)
The shutdown of a station doesn’t lead to the global node initialization except if a complete function
can’t be anymore offered.
A centralized defense function in the control is provided:
To launch a global node initialization if one of the principal functions of the HLR is in outage (no
more instance of these functions),
To send an alarm if more than X % of a function is out of service.
The outage of the two controls stations leads to a global initialization of the node.
SDM level defense is handled by:

Hardware defense,

29/83
Software defense.
Depending on the faults detected, defense mechanisms can be applied on the 8650 SDM applica-
tions.
6.4.2.1 HARDWARE DEFENSE

The 8650 hardware defense is provided by the ATCA platform:
Duplication of hardware,
Duplex configuration,
Link protection switching,
Hardware monitoring.
Duplication of hardware
Beside geographical redundancy mode, the critical elements of a node in the 8650 SDM platform
are duplicated:
Database updates are secured on 1+1 Database stations,
Control Station are secured in 1+1 mode
Connectivity is secured in N+1 load sharing with RT stations,
Ethernet switching is secured in 1+1 mode,
Routers are secured in 1+1 mode
Hardware monitoring
The hardware components of the HLR are permanently monitored by cyclic polling of the board
status registers.
When the system detects a defective board:
LEDs on the board signal the fault,
The active subsystem switches over to the standby subsystem according to the type of board
concerned.
6.4.2.2 SOFTWARE DEFENSE

SDM software defense is based on:
Software duplication,
Application Software Package (ASP) supervision.
ASP Supervision
The SUPervisor Application Software Package (SUPASP) supervises the ASPs.
ASP supervision involves monitoring the operation of the applications. An ASP is supervised in both
active and standby subsystems.
The SUP ASP centralizes application ASP defense actions:
Reloading of an ASP,
Subsystem switchover,

30/83
Shutdown of an ASP.
6.4.2.3 SDM DEFENSE MECHANISMS

SDM defense mechanisms concern:
Defense against traffic overloads,
Data restore,
System restart and restore.
Defense against traffic overloads

When traffic reaches a high level, the 8650 SDM takes measures in increasing order depending on
the level to avoid any overload on the system. Two thresholds are set in the system: when the 1st
threshold is crossed a warning may be sent to the operator, when the 2nd threshold is crossed in-
coming requests start to be rejected and an alarm may be sent to operator to notify the starting of
regulation.
New requests are rejected selectively depending on the overload level. Functions that have the least
influence on quality of service are rejected first. At maximum level all incoming requests are rejected
without Protocol decoding.
6.5 NETWORK LEVEL DEFENCE IN COMPACT CONFIGURATION
SDM can be configured in a real-time mated-pair site redundancy in order to prevent from a site
disaster.
All the necessary data are replicated in the mated pair of 8650 SDM and updated in real-time
through the asynchronous replication feature.
The database of the standby 8650 SDM is always coherent. The data caches of the real time are
always refreshed.
Due to this synchronization, a standby 8650 SDM is able to switch to an active state at any time
upon automatic switchover, or operator controlled switchover.
Data synchronisation and replication
HLR HLR
Active Standby
SS7
Traffic
Traffic NETWORK

31/83
Figure 11. Example of HLR Mated pair implementation

32/83
6.6 NETWORK LEVEL DEFENSE IN DISTRIBUTED CONFIGURATION
In Alcatel-Lucent distributed 8650 SDM, the network defence mechanisms are as follows:
Front End nodes: FEs work in load sharing mode. If a Front End fails, the signaling traffic is
switched to the remaining FEs thanks to the SCCP routing mechanisms in the case of HLR
applications.
DB Nodes: DB Nodes work in Active/Standby mode, ie when a DB Node becomes unavailable,
the Standby node will take over automatically
When both DB nodes are working, one DB node is said primary from the FE point of view. It handles
requests from FE and replicates the database modifications on the secondary DB Node. A heartbeat
guarantees that the link between the two DB Nodes is active.
Each DB Node hosts a DB supervisor that notifies regularly its status to the other DB Node and the
Front End DB supervisor Agent:
Status has 3 values:
Read/write: the DB Node is Active,
Read Only: the DB Node is standby,
Maintenance: the DB Node cannot accept Read or Write requests.
This product architecture ensures service continuity in an automatic way and takes into account the
following network events:
A complete unavailability of a DB Node
A complete unavailability of one FE Node
A complete unavailability of all Nodes in the same Site
IP link failures as long an IP connectivity between FE and DB nodes is possible
8650 SDM solution integrates a 3 sites redundancy in Active/Stand-by/Stand-by mode in order to

have at any time 3 copies of Databases in different locations.
6.7 DEFENCE
The detection and the confinement notification operations take less than 100 milliseconds.
Less than 1 second is required to reconfigure and recover the failed services on another board.
The global initialisation duration (time between the platform reset from disks and the first established
call) is less than 10 minutes for large capacity systems.

33/83
6.8 RESILIENCE
8650 SDM availability, including hardware and software failures, is evaluated at 99,999 %, taking
into account the following conditions:
Mean Time To Repair (MTTR) for immediate intervention: 4 hours,
Mean Time To Repair (MTTR) for deferred intervention: 12.5 hours.
In mated pair compact or distributed configuration, the 8650 SDM availability, including hardware
and software failures, is evaluated at 99,9999 % and the Mean Time To Repair (MTTR) for deferred
intervention can be up to 72 hours.

34/83
7 SDM APPLICATION OVERVIEW DESCRIPTION
7.1 INTRODUCTION
8650 SDM solution is already allowing support of a set of application on a single platform system
and is expanding with future release to manage a fully comprehensive set of applications like:
• GSM/UMT HLR
• IMS HSS application,
• SLF,
• MNP application,
• EIR application,
• LTE application
• Open Data storage Server application2.
Please always refer to the product roadmap and feature list for information about specific services
ad configurations supported in various Alcatel-Lucent 8650 SDM product releases. The following
planning summary is subject to change, without further notice.
SDM 1.1 (GSM/UMTS HLR)
SDM 2.0 (IMS-HSS Only)
SDM 2.1 and SDM 2.1 SU1(GSM/UMTS HLR, IMS-HSS, EIR, MNP)
SDM 2.1 SU3 (GSM/UMTS HLR, IMS-HSS, EIR, MNP, LTE)
SDM 3.0 (GSM/UMTS HLR, IMS-HSS, EIR, MNP, LTE, Open Data Storage)
SDM 3.1 (GSM/UMTS HLR, IMS-HSS, EIR, MNP, LTE, Open Data Storage)
This chapter provides an overview of the application portfolio of 8650 SDM.
7.2 GSM/UMTS HLR APPLICATION OVERVIEW
The AuC module of the GSM/UMTS HLR application stores and provides security features for GSM,
UMTS and IMS network. AuC is involved in:
Authentication & security key management,
Access link ciphering,
Secure UMTS and GSM operation,
Access link integrity protection.
2 This application is only available in distributed configuration.

35/83
The AuC stores individual identification keys linked to the International Mobile Subscriber Identity
(IMSI), calculates the security triplets (GSM) and quintuplets (UMTS) required for the authentication,
integrity and ciphering procedures, and sends them to its client.
These clients are:
The HLR for the security at CSCN (MSC/VLR) and PSCN (SGSN) levels
The IMS HSS for the security at IMS level
When the user to be authenticated is not directly identified by an IMSI (e.g. as is the case for an IMS
user), the client (e.g. IMS HSS) has first to derive the IMSI of the user from the user identity within the
service. For IMS, if the User Identification card (UICC) does not contain an ISIM (IMS) application,
then the IMSI is derived using rules described in 3gpp TS 23.003. Otherwise this is done based on a
mapping table.
The HLR is a database that manages the Mobile Subscribers.
The HLR application stores and makes available to Mobile network all standardized subscription
information needed to setup GSM, SMS, UMTS or GPRS calls.
The HLR application offers the following functions:
Mobility Management: support of user mobility
Call establishment support: supports of the call establishment procedures for Mobile networks.
User security information generation: the HLR generates user authentication, integrity for the
Mobile networks
Service authorization support: the HLR provides basic authorization for MT call establishment
and service invocation. Besides, the HLR updates the appropriate serving entities (i.e. MSC,
SGSN) with the relevant information related to the services to be provided to the user.
Service Provisioning Support: the HLR provides access to the service profile data for use within
the Mobile network.
It contains the information needed to identify and locate the Mobile Subscribers.
For each subscriber, the HLR stores data that can include:
Subscription data (IMSI, Mobile Subscriber ISDN Number (MSISDN), roaming restriction, basic
services subscribed to, etc.),
General Packet Radio Service (GPRS) data (network access name, Packet Data Protocol (PDP)
contexts, PDP addresses, etc.),
The administrative state of the subscriber,
User Equipment (UE) type,
Security triplets, or quintuplets depending on the subscriber type (GSM or UMTS),
Location data,
Subscribed supplementary services,

Call trace data,
Operator Determined Barring (ODB) restrictions,
Customized Applications for Mobile network Enhanced Logic (CAMEL) service data.

36/83
The location data are permanently updated through network function involving the terminal, the
radio and the core network. This function, called location update procedure, enables the network to
know the location of a mobile subscriber at any time.
These location data offer the subscriber continuity of service throughout the authorized coverage
area as the HLR can supply call routing information to all network components like:
The Gateway MSC (GMSC). The GMSC uses this information to establish terminating voice and
data calls.
The Gateway GPRS Support Node (GGSN). The GGSN uses this information to establish PDP
context initiated by the network. This PDP context stored all information to route the Packet Data
Unit (PDU) for each terminating GPRS connections.
The Short Message Service Center (SMS-C) and manages message-waiting indications. The
SMS-C uses this information to deliver originating or terminating short messages it has stored.
The HLR provides some additional functions like:

Translation: the HLR contains translation tables, which it scans for the rerouting of certain calls
according to the signaling information assigned to the call.
Call tracing: Call tracing is a network function that enables operators to trace activities of mobile
subscribers as a result of events (for example, an originating call) occurring within a PLMN.
Fraud prevention: Fraud prevention provides a means of identifying counterfeiting of a USIM
card or forwarding for international calls (with the intention of not paying).
Supplementary services data processing: a supplementary service is an additional service that
modifies or enhances a basic telecommunications service (like Call forward, Call deflection,
Closed User Group…)
Operator Determined Barring: the operator can block, for administrative reasons, the ability of a
mobile subscriber to Roam, Receive calls, Make outgoing calls, Manage their supplementary
services or access GPRS services.
Roaming restriction processing: the regional subscription function enables operators to restrict
mobile subscriber services to one or more location areas.
Mobile number portability: when portability is offered, the Subscriber Number (SN) must include
the National Destination Code (NDC). HLR provides Flexible NDC allowing an NDC of 2 or 3
digits. The maximum number of digits in the SN field is extended to allow up to 14 digits (instead
of the standard 10).
CAMEL data: CAMEL is a set of definitions for IN access developed specifically for mobile
networks. It enables subscribers to use the services to which they have rights, even when they are
traveling in foreign networks.
Observation: Observation is a set of network functions that enables operators to control the
quality of the service offered to subscribers and to control network traffic flow.
7.3 IMS HSS APPLICATION OVERVIEW

37/83
The IMS HSS application stores and makes available to multimedia call servers all standardized sub-
scription related data needed to setup multimedia sessions. It is part of the IP Multimedia Subsystem
(IMS) that builds on a packet-switched or any IP network and introduces a new layer in the network:
the session layer. This new layer enables new packet-switched/IP services based on multimedia ses-
sions, for example, video telephony.
The IMS HSS application offers the following functions:
Mobility Management: support of user mobility through IM CN subsystem
Call and/or session establishment support: supports of the call and/or session establishment
procedures in IM CN subsystem. For terminating traffic, it provides information on which call
and/or session control entity currently hosts the user
User security information: In conjunction with an external AuC, the HSS supports user
authentication, integrity for the IM CN subsystem
User security support: supports of the authentication procedures to access IM CN subsystem
services by storing the secret key used for authentication and integrity and by providing the
generated authentication vectors to the CSCF on request
Access authorization: the IMS HSS authorizes the user for mobile access when requested by the
CSCF, by checking that the user is allowed to roam to that visited network.
Service authorization support: the IMS HSS provides basic authorization for MT call/session
establishment and service invocation. Besides, the IMS HSS updates the appropriate serving
entities (i.e. CSCF) with the relevant information related to the services to be provided to the user.
Service Provisioning Support: the IMS HSS provides access to the service profile data for use
within the IM CN subsystem.
Subscriber Profile/Policy Data Repository (SPR): the IMS HSS supports the storage of IM CN
Subsystem user related data, and provides access to these data through the Sp reference point.
IMS Application Severs (AS) individually able to provision such subscriber data (also known as
Transparent data) and store it with IMS HSS, as part of the user’s IMS subscription profile. IMS
HSS passively receives, stores, updates and forwards such transparent data in response to
queries from the network, but does not actively parse or process or act up on such information.
The IMS HSS also incorporates the Subscriber Locator Function (SLF) which can be activated
either in the stand-alone mode, or in co-resident mode along with IMS-HSS. The initial release
supports SLF only Redirection as defined in the standards (Dx).
The IMS HSS handles different kind of users:

Mobile IMS user: The user is a 3GPP user that complies to the standards, in particular:
PSI (Public Service Identifier) users

Fixed IMS users with user profile data model compatible with 3GPP also including supplementary
attributes
The PES subscriber (PSTN Emulation Service) attached to an Access Gateway (AGW)
The IMS HSS holds the authentication data for each subscriber. The IMS HSS supports authentication
At registration time,

38/83
Possibly at multimedia session set up.
Multiple simultaneous authentications of different types and on different interfaces can be performed
by the S-CSCF and the Application Servers on a user identified by the Private User Identity. The au-
thentications methods allowed for a given user are the Digest –AKA, SIP-Digest, Early IMS authenti-
cation, and NASS-IMS bundled authentication.
The authentication requests may come from a S-CSCF or Application Servers. To handle the multi-
plicity of authentications, the IMS HSS manages, per Private Identity, a list of authorized authentica-
tion methods.
7.4 SUBSCRIPTION LOCATOR FUNCTION (SLF) OVERVIEW
IMS HSS application incorporates a built-in SLF which can be configured and exercised either in a
stand-alone SLF-only mode or in a co-resident mode in conjunction with IMS-HSS functionality. Al-
catel-Lucent 8650 SLF is available only as a satellite asset, in the context of an Alcatel-Lucent 8650
IMS-HSS offer.
Depending on the strategies for network design and/or operations or the capacity considerations,
the IMS customers may deploy multiple HSSs in their networks to accommodate all their IMS sub-
scription profiles. For such cases, CSCFs/ASs in the home network must have a way to know where
a IMS subscription is for sending the Cx/Sh requests for the subscription to the home HSS, i.e. the
resolution capability from user identifiers to the home HSS. To address this need, 3GPP specifica-
tions introduced SLF as the logical entity to fulfill the capability.
The SLF is a resolution mechanism that provides the IMS HSS name where the profile data of a given
subscriber can be found.
The SLF enables the call control server and the application servers to get the address/identity of the
IMS HSS, that holds the subscription data for a given user identity when multiple and separately ad-
dressable HSSs have been deployed by the network operator.
When there are multiple HSSs are deployed in service provider's network, Subscription Locator Func-
tion (SLF) is required to identify the specific HSS to be queried. The SLF:
Is queried by the I-CSCF during the Registration and Session Setup to get the name of the
HSS containing the required subscriber specific data. Furthermore the SLF is also queried
by the S-CSCF during the Registration.
Is queried by the AS in conjunction with the Sh interface operation to get the name of the
HSS containing the required subscriber specific data.
Is queried by the 3GPP AAA server to get the name of the HSS containing the required sub-
scriber specific data.
In addition, SLF will be accessed via the Dw interface (part of Wx interface) by the 3GPP
AAA Server, in a future release.

39/83
The identity of the user name is extracted from the received requests received over these interfaces.
The SLF manages a database where the IMS HSS name is associated to each user. The identities
that can be used are (in compliance with 3GPP TS 23.003)
The Private Identity
The Public Identity
The IMSI
THS MSISDN
From the viewpoint of routing behavior or position in DIAMETER call path, SLF may work within the
following two different modes:
Redirect mode (Available in Current Release):

In this case, SLF will work like a DIAMETER redirect agent. For any incoming Cx/Sh request, SLF
will query its own routing tables for the home HSS the user identity in the request belongs to.
Upon successfully, the SLF will return a redirect response with the HSS’ address to the originator
CSCF/AS, and then the originator will forward the request to the HSS for further handling. In
such a case, CSCF/AS is also required to be ready for receiving such redirect responses to con-
tinue the signaling procedures.
Relay mode (Planned for a Future Release):

In this case, SLF will work like a DIAMETER proxy/relay agent. Compared to the redirect mode,
SLF will always be on the call path until the final response for the original request is got back
and then returned to the originator, so it must keep at least the transactional state as a
DIAMETER stateless agent during the period. The advantage of the mode is that SLF will be
transparent to CSCF/AS exactly so no implementation enhancements will be required on the
side of the existing CSCF/AS.
7.5 MNP APPLICATION OVERVIEW
Mobile Number Portability (MNP) is the ability for a UMTS or GSM mobile subscriber to change the
subscription network within a portability domain whilst retaining his/her original MSISDN or
MSISDNs. This requirement implies a porting process where the donor, number range owner and
recipient networks shall update their relevant network elements in order to perform the porting. After
the porting process is complete, the subscription details related to the ported DN on the donor net-
work can be deleted. Therefore, only the number range owner network and the recipient network
are involved in the MNP solution for support of service to the ported subscriber.

40/83
The translation standard mechanisms route the call or message destined to a ported subscriber to
the network that handles the subscriber number range (NRON).
The MNP function permits to re-route to the correct direction:
The calls (by rerouting of SRI messages)
The non-call related signaling (e.g. SRI for SMS, SRI for Optimal Routing).
The MNP makes use of a Number Portability Data Base (NPDB), which is accessed through a SCCP
relay entity.
According to the GSM standards (02.66, 03.66), two access methods have been defined:
Architecture based on the Intelligent Network: subset of IN-CS1 operations (INITIALDP,
Connect, Continue) – Only for call related,
Architecture based on an SCCP relay entity (MNP – Signaling Relay Function (SRF)) – For
call related and non-call related signaling (SMS, OR).
As a consequence of MNP, the Directory Number of a mobile subscriber may no longer explicitly
identify the subscription network of that subscriber.
Additional routing information is needed: the Routing Address, specified by the Network Routing
Number (RN) and the Directory Number (DN).
Alcatel 8650 SDM supports the MNP SRF solution.

The MNP-Signalling Relay Function (MNP-SRF) provides re-routing capability at the SCCP level of
signalling messages using the MSISDN as called party number. The MNP-SRF obtains routing infor-
mation from a database to identify the subscription network associated with a particular national
MSISDN.
The Number Range Owner Network must support the MNP-SRF.
The MNP-SRF may be used in the originating network to directly route the message to the
recipient network.
In the recipient network, the MNP-SRF is used to re-route SCCP based signaling messages to the
correct HLR.

41/83
The following routing conventions are defined:
A message (1) originated outside the portability domain, is received by the Number range holder
network. The Number range holder network routes the message onward to the recipient network
If a message is originated in a PLMN, inside the portability domain, which supports "direct
routing" this PLMN routes directly the message (2) to the recipient network.
If a message is originated in a PLMN, inside the portability domain, which only supports
"indirect routing" this PLMN routes the message (3) to the Number range holder network. The
Number range holder network routes the message onward to the recipient network.
PSTN
Number Range
Originating PLMN (1) Incoming Call Owner Network
(3) Indirect Routing
Or GMSC
GMSC
Recipient Network
(2) Direct Routing
VMSC
GMSC
7.6 EIR APPLICATION OVERVIEW
With the increasing number of mobile handsets theft, it becomes a real competitive advantage for
operators to have the means to fight against the usage of stolen terminals. The EIR application plays
a key role in that respect and allow controlling this type of fraudulent usage.
The application manages lists of equipments that are considered to be fraudulent. These lists can be
built and managed by the operator with create, delete operations via standard platform provisioning
interface (bulk, corba, …). Tooling is also included to synchronize black listed equipment with the
central IMEI Database (IMEI DB). The IMEI database is a global central database containing basic
information on serial number (IMEI) ranges of millions of GSM and 3G devices (e.g. mobile phones,
laptop data cards).

42/83
When synchronizing with central IMEI database, the operator can:
• Select given entries of given operators
• Exclude specific IMEI ranges
• Manage automatically or manually synchronization of back/white list to the platform.
This application EIR is based on usage of Check IMEI MAP Phase 1, Phase 2, and Phase 3. Option-
ally the IMSI can be provided as part of this message as defined in 3GPP standard. This additionally
can allow detecting fraudulent usage based on patterns like for example an IMEI that changes fre-
quently association with an IMSI.
To manage these requirements EIR application:
• Processes Check IMEI MAP phase 1, Phase2, Phase3 messages,
• Check the IMEI information against list of black and/or white listed equipment,
• Manage IMSI (Subscriber)/IMEI (handset) association,
• Manage counts of events of patterns to report fraudulent indicators.
This application EIR manages also 2 other lists:

• IMEI duplicate list to manage situations with cloned IMEI or to cover IMEI erroneously entered
in IMEI DB (local fix to be applied while correction within IMEI DB is pending
• IMSI override list to allow call of specific IMSI (valid user) whatever the status of IMEI.
7.7 LTE APPLICATION
LTE (Long Term Evolution) domain is an extension of 3GPP PS (Packet Switch) domain and is sup-
ported as an application of 8650 SDM portfolio. The scope of LTE is to improve efficiency, lower
costs, to make use of new spectrum opportunities, and better integrate with other open standards.
LTE subscribers can be named 4G subscribers. 8650 SDM LTE 3GPP HSS application is integrating
S6a and SWx interfaces:
• S6a is interface between SDM and MME (Mobility Management Entity) to manage UE’s MME
registration location & status, authentication support, and subscriber profile downloads to the
MME.
• SWx is interface between SDM and AAA to enable non-3GPP access to the EPC.
LTE provisioning for 4G subscriber profile is integrated within current 8650 SDM provisioning struc-
ture. Single OAM command from OSS is needed to create subscriber within SDM Database, what-
ever the wireless access (2G/3G or 4G). All current provisioning interfaces are supported (SOAP
CM, CORBA, Bulk).

43/83
The LTE customers may deploy multiple HSSs/EIRs in their networks to accommodate all their sub-
scription profiles. For such cases, MME/AAA/SGSN etc in the home network must have a way to
know where the requested subscription is for sending the S6a, SWx and S13/S13’ requests for the
subscription to the home HSS/EIR, i.e. the resolution capability from user identifiers to the home
HSS/EIR
The SLF enables the MME/AAA/SGSN to get the address/identity of the IMS HSS, that holds the sub-
scription data for a given user identity when multiple and separately addressable HSSs have been
deployed by the network operator.
7.8 OPEN DATA STORAGE APPLICATION
Alcatel-Lucent 8650 SDM is intended to be the central repository of all subscription data of carrier’s
network, either mobile or fixed.
For that purpose, Alcatel-Lucent has designed an opened platform and opened database framework
in order to support multiple subscription types (2G, 3G, LTE, IMS) and be able to integrate other
subscription databases for 3rd party application like GPRS, MMS, AAA … This is enabled thanks to a
hierarchical data model view that allows the integration of new 3rd party application subscription
and identities attached to this Subscription Profile.
Access to all subscription data is made possible through a standard LDAP interface. LDAP server
integration allows support of the following features:
Authentication of LDAP Clients.
Data related to GSM/UMTS subscription (HLR application), LTE subscription, IMS subscription will
remain under Alcatel-Lucent control and access will be made available to 3rd party application
access via LDAP. Access will be limited to read only operations.
rd
Access Control to manage LDAP read and write access over 3 party application subscriptions.
Every LDAP access will be result in a transaction to the Database to guarantee data integrity. This
mechanism is relying directly on 8650 Database Framework and is essential in a multi-
application environment whit multiple reader/writers to the same data.
LDAP subscription location: LDAP client is totally transparent to the location of Subscriber
information in a particular Database node. Location of the subscriber is relying on internal
Database framework. This is completely hidden to the client for an easy and fast integration.
A 8650 SDM LDAP SDK (Software Develoment Kit) is provided to enable a 3rd party application
to create and extend its own LDAP database on the 8650 SDM Back-end:
• It can design its own schema,
• It can add a new DIT in an existing MySQL database
• It can extend online the existing LDAP schema with compatible modifications:
o Add new DIT
o Add subtree in DIT to a terminal DN
o Add object class
o Add attribute to an entry

44/83
Specific extension is proposed to the 3rd party for added-value features, in particular the use of
“Data profile” feature.
3rd party can benefit from following added-value features:
• Attribute size and number of values (redefinition by the customer of default size and val-
ues)
• Static RDN type (specify a RDN as a static entry prevents from creating a table when
there is no attributes bound to this entry - gain size)
• Load data profile (only in case of mono NRG – bind an attribute to an entry; a Data
profile defines a set of entries from a base entry. It allows to retrieve all the entries be-
longing to a Data Profile through an unique LDAP search query on the Data Profile base
entry )
• Local data (for performance purpose- DN put in cache)
• Exclusion of standard schemas (if customer does not want to use default standard sche-
mas cosine and inetorgperson)
To be able to create or extend its database, 3rd party needs to have:
• DDM LDAP SDK installed
o prerequisite: Eclipse IDE including XML feature (Galileo), Java 1.5 or newer,
linux.
o Components: APACHE LDAP browser , APACHE LDIF editor, APACHE SCHEMA
editor, UnboundId library, java library for ant processing (Java Secure channel)
o Procedure: installation via the Eclipse Install/Update manager
• DDM 3rd party project created, via the menu of Eclipse workbench.

45/83
8 SUBSCRIBER ADMINISTRATION
Operators can use the Customer Care and Billing System to administer subscriber data. To do this,
operators issue administration-related commands (such as create, delete, modify subscriber, etc.,)
from the CCBS to the 8650 SDM, either
Through Corba or SOAP for all with unitary commands
Through XML over https for mass management operations
An automatic network mechanism insures integrity inside the Alcatel-Lucent 8650 SDM database.
Data changes carried out in the Alcatel-Lucent 8650 SDM are automatically transferred to the rele-
vant Network Elements, if necessary. Certain categories of operator commands are reserved for
authorized operators only.
8.1 SUBSCRIBER DATA MODEL
The subscriber data model of the Alcatel-Lucent 8650 SDM is X500 like.
The general user profile is 3GPP compliant.
Other Identity IMSI MSISDN IMPI IMPU
Subscription Profile
GSM Service Profile
IMS Service Profile
WLAN Service Profile
Other Service Profile
Figure 12. Flexible 3GPP Data Model
The description and declaration of database schemes, business entities, interfaces, management
operations are performed through external XML description files offering the highest level of flexibil-
ity.
This architecture provides the right structure to add new subscriptions and provide the right founda-
tion to manage easy introduction of new applications.

46/83
8.2 MANAGEMENT INTERFACES
Alcatel-Lucent 8650 SDM provides high performances in term of management capabilities thanks
to:
CORBA /SOAP based machine-machine interface,
Object oriented OAM agent,
Use of Commercial Off the Shelf database.
It provides high performances for subscriber management (see section 11.5 for performance de-
tails).
Subscription models and user profiles are managed via GUI interface in order to access to profile
parameters required to create, modify, search and query records in the database.
Same Web based Look&Feel for all management application with on-line help and documentation
are provided.
Alcatel-Lucent 8650 SDM provides opened interfaces:

IP Based management interfaces,
Machine-machine interface instead of man-machine interface,
New protocol support: Corba, HTML, presentation IDL, XML, SOAP
Allow control access to Database information. Access control permits to operator to create
different accounts (login/pwd) with specific rights on domain/interface/operation (as an
example, right to create subscriber…).
Same Interface for: Graphical User Interface, Scripts, external management applications
(operator written management application).
LDAP in reading mode.
8.3 MASS MANAGEMENT
The mass management service provides:

The shared profile management (in this case, a modification in the shared profile will be apply
immediately for all subscribers attached to this profile)
The bulk management service compliant to 3GPP through XML files
Parallel execution of xml bulk script for efficient provisioning
The fast database modification (modification/addition of parameter values in a range of entries

matching a set of criteria, …)
The fast consultation and audit of a list of subscribers matching a set of criteria
Calendar service provides the capability to schedule bulk management jobs immediately, at a given
time or periodically.

47/83
9 INTERFACES AND PROTOCOLS
This section describes the network interfaces for GSM/UMTS HLR application and related signaling
protocols.
Next figure illustrates the signaling links and protocols between the Alcatel-Lucent 8650 SDM and its
environment including all applications of 8650 SDM portfolio.
GMLC
MAP Lh
XMC CCBS
MAP E
SMSC IP
MAP C,D
MSC/VLR
MAP Gr
SGSN
MAP J
IP IP
X1 Interception
SCP
Radius Gi EQPT
GGSN
X2
Diameter Cx/Dx
CSCF
IP
Diameter Sh/Dh
IMS AS 8650SDM
Diameter Zh
BSF Diameter S6a, S13
MME IP
SIGTRAN CEIR
Diameter S13’
S4SGN Supported
Diameter SWx IP
8950 SDM
LDAP
AAA MAP EXPERT
Figure 13. Alcatel-Lucent 8650 SDM interfaces
9.1 PHYSICAL INTERFACES
For signaling interfaces, the Alcatel-Lucent 8650 SDM supports:

Low and High Speed links connections.
E1 and T1 connectivity.
ETSI and ANSI SS7 stacks,
Ethernet IP,
SIGTRAN (M3UA/SCTP/IP) signaling for transporting MAP/SS7 over IP.
SIGTRAN is using SCTP protocol (IP port 2905) over Ethernet links on Real Time blades.

48/83
9.2 DESCRIPTION OF GSM/UMTS HLR INTERFACES
9.2.1 INTERFACE BETWEEN HLR AND SMS-C (E INTERFACE)
The interface between the HLR and the Short Message Service-Service Center (SMS-C) handles short
messages.
The HLR and the SMS-C use the Mobile Application Part (MAP) protocol to communicate. This is
based on Signaling System Nº7 (SS Nº7).
9.2.2 INTERFACE BETWEEN HLR AND MSC/GMSC (C INTERFACE)
The interface between the HLR and the Mobile services Switching Center (MSC)/Gateway MSC
(GMSC) is used when an MSC/GMSC receives a call from a subscriber in the fixed network or from
a User Equipment (UE). The MSC/GMSC interrogates the HLR to obtain the information needed to
route the call.
The HLR and the MSC/GMSC use the MAP protocol to communicate. This is based on SS Nº7.
9.2.3 INTERFACE BETWEEN HLR AND VLR (D INTERFACE)
The interface between the HLR and the Visitor Location Register (VLR) is used when:
A UE enters an area managed by another VLR. The HLR is informed of this so that the new
location of the UE can be updated.
The VLR asks the HLR for a set of authentication triplets or quintuplets.
The HLR sends an update request to the VLR or vice versa (for example: supplementary services
activated by the operator or by the mobile subscriber).
The HLR asks for a Mobile Station Roaming Number (MSRN) from the VLR.
The HLR and the VLR use the Mobile Application Part (MAP) protocol to communicate. This is based
on SSNº7.
9.2.4 INTERFACE BETWEEN HLR AND SGSN (GR INTERFACE)
The interface between the HLR and the Serving GPRS Support Node (SGSN) links the Circuit-
Switched Core Network (CSCN) to the packet switched core network.
The interface between the HLR and the SGSN is used when the:
SGSN is requesting a set of authentication triplets or quintuplets from the HLR,
HLR is informed of the UEs new location,
SGSN initiates the UE Purge procedure to the HLR, following an operator command or
automatically after a period of UE inactivity. The UE Purge procedure informs the HLR that the
data of the detached UE is deleted from the SGSN.
The HLR must modify or delete the subscription data in the SGSN,

49/83
The HLR restarts and sends a reset message to each SGSN, where at least one of the mobile
stations if the HLR is registered.
The HLR and the SGSN communicate using the MAP protocol. This is based on SS Nº7.
9.2.5 INTERFACE BETWEEN HLR AND SCP (J INTERFACE)
The interface between the HLR and the Service control Point (SCP) is used in the context of:
Any Time Interrogation (ATI), to enable the SCP to check the location of the UE and/or its state,
Unstructured Supplementary Service Data (USSD) to enable:

• The UE to modify or interrogate SCP data,
• The SCP to send an interrogation to the UE.
Active Location Retrieval (ALR) to determine the location of a UE whether the UE is reachable or
not reachable.
The HLR and the SCP use the MAP protocol to communicate. This is based on SS Nº7.
9.2.6 INTERFACE BETWEEN HLR AND GMLC (LH INTERFACE)
The interface between the HLR and the GMLC is used for the Location Services (LCS) Mobile Termi-
nating-Location Report (MT-LR) function, which allows a Gateway Mobile Location center (GMLC) to
request the location of a UE.
The HLR and the GMLC use the MAP protocol to communicate. This is based on SS Nº7.
9.3 DESCRIPTION OF IMS-HSS & SLF INTERFACES
9.3.1 INTERFACE BETWEEN IMS-HSS AND CSCF (CX INTERFACE)
The Cx interface to CSCF is compliant to the 3GPP 29.228 V6.13.0 & 29.229 V6.9.0 standards,
with extensions to support unregistered originating registration and Display Name in IFC per R7
29.228 V7.60. The Cx interface supports:
1. User Equipment (UE) authentication data
2. User service profile download including IFC (Intitial Filter Criteria ) and charging server ad-
dresses
3. Subscriber location and registration status information
4. Provisioning of CSCF capabilities information

50/83
9.3.2 INTERFACE BETWEEN IMS-HSS AND IMS-AS (SH INTERFACE)
The Sh interface to IMS-AS (Application Servers) is compliant to the 3GPP 29.328 V7.4.0 and 3GPP
29.329 V7.3.0 standards, with exception of support DSAI, Expiration-Time, and subscription of iden-
tity-set. The Sh interface supports:
Data handling procedures including (a) SPR Functionality (Subscriber Profile/Policy/Transparent-

Data Repository), (b) Downloading data from the HSS to an AS, and (c) Update of data in the
HSS by AS
Subscription/notification procedures such as (a) AS subscribes notifications from the HSS for HSS
data change, and (b) HSS notifies an AS of changes in data for which the AS previously had sub-
scribed.
9.3.3 INTERFACE BETWEEN IMS-HSS AND BSF (ZH INTERFACE)
The Zh interface to BSF (Bootstrapping Server Function) is compliant to 3GPP 29.109 V7.9.0 for
GUSS data. The Zh interface supports BSF queries for (a) GUSS data based on Diameter protocol
and (b) User’s authentication data.
9.3.4 INTERFACE BETWEEN SLF AND CSCF & IMS-AS (DX INTERFACE)
The Cx interface to CSCF/ IMS-AS is compliant to the 3GPP 2006-12 3GPP 29.228 V6.13.0 &
29.229 V6.9.0 standard. The Dx interface supports queries for subscriber’s HSS address.
The 8650 SDM SLF is accessed via the Dx interface by the CSCF, via the Dh interface by the AS, in
the initial IMS-HSS release
Dx and Dh interfaces share the same set of DIAMETER application identifier, command codes and
AVPs as Cx/Sh respectively. As a result, CSCF/AS can send the same Cx/Sh messages to SLF as
those to HSS with the enhancement of handling Diameter redirection.
9.3.5 INTERFACE BETWEEN IMS-HSS AND 8670 GUP SERVER (RP INTERFACE)
The Rp interface to Alcatel-Lucent 8670 GUP server is compliant to the 3GPP SOAP XML GUP/Rp TS
29.240 standard. The 8670 GUP server in-turn interfaces with upstream OSS in the network using
the SOAP/XML GUP/Rg interface specification.

51/83
9.4 DESCRIPTION OF LTE INTERFACES
9.4.1 INTERFACE BETWEEN 3GPP HSS AND MME (S6A INTERFACE)
The interface between the 3GPP HSS and the MME (Mobility Manager Element) in the Enhanced
Packet Core is S6a and is based on DIAMETER.
The interface between the 3GPP HSS and the MME is used when the:
MME is requesting a set of authentication triplets or quintuplets from the 3GPP HSS,
3GPP HSS is informed of the UEs new location and manages registration,
3GPP HSS initiates the UE Purge procedure to the HLR, following an operator command or
automatically after a period of UE inactivity.
The 3GPP HSS must modify or delete the subscription data in the MME when subscription is
modified.
9.4.2 INTERFACE BETWEEN 3GPP HSS AND AAA (SWX INTERFACE)
The interface between the 3GPP HSS and the AAA in the Enhanced Packet Core is SWx and is based
on DIAMETER.
The interface between the 3GPP HSS and the AAA is used to:
Manage/store UE’s 3GPP AAA registration location/status
Enable non-3GPP accesses to the EPC
Generate EAP AKA authentication vectors with enhanced CK’ and IK’
Download subscriber profile to 3GPP AAA
Handle Subscriber data change
9.5 DESCRIPTION OF EIR INTERFACES
9.5.1 INTERFACE BETWEEN EIR AND MSC (F INTERFACE) AND GGSN (GF INTERFACE)
The interface between the EIR and the MSC deals with checking IMEI within EIR DB.
The EIR and the MSC (as well GGSN) use the Mobile Application Part (MAP) protocol to communi-
cate. This is based on Signaling System Nº7 (SS Nº7).
Interface is based on Check IMEI MAP Phase 1, Phase 2, and Phase 3 message.

52/83
9.5.2 INTERFACE BETWEEN EIR AND MME (S13 INTERFACE), EIR AND SGSN (S13’
INTERFACE)
The interface between the MME and EIR support the diameter based S13 interface for ME identity
check per 2010-03 standard 29.272 V8.6.0.
The interface between SGSN and EIR support the diameter S13’ interface for ME identity check per
2010-03 standard 29.272 V8.6.0.
9.5.3 INTERFACE BETWEEN EIR AND CENTRAL EIR (CEIR INTERFACE)
The interface between the PLMN EIR and Central EIR is defined by GSM MoU Association in docu-
ment “Central EIR/ EIR Administration System Data Interface Definition”.
This interface allows to synchronize an 8650 SDM based EIR application with the central database
that centraliezes all IMEI infor
9.6 DESCRIPTION OF MNP INTERFACES
9.6.1 INTERFACE BETWEEN MNP AND HLR
The interface between the MNP and HLR handles terminating call messages.
The MNP and the HLR use the Mobile Application Part (MAP) protocol to communicate. This is based
on Signaling System Nº7 (SS Nº7).
9.6.2 INTERFACE BETWEEN MNP AND SMS-C
The interface between the MNP and the Short Message Service-Service Center (SMS-C) handles short
messages.
The MNP and the SMS-C use the Mobile Application Part (MAP) protocol to communicate. This is
based on Signaling System Nº7 (SS Nº7).
9.6.3 INTERFACE BETWEEN MNP AND MSC/GMSC
The interface between the MNP and the Mobile services Switching Center (MSC)/Gateway MSC
(GMSC) is used when an MSC/GMSC receives a call from a subscriber in the fixed network or from
a User Equipment (UE). The MSC/GMSC interrogates the MNP to obtain the information needed to
route the call when MNP is activated in the portability domain.
The MNP and the MSC/GMSC use the MAP protocol to communicate. This is based on SS Nº7.

53/83
9.7 INTERFACE BETWEEN 8650 SDM AND NETWORK MANAGEMENT
The 8650 SDM allows interfacing with 1300 XMC (the Cross-Domain Maintenance Centre for Core
Network) to manage centrally a geographically deployed solution.
The 1300 XMC manages administration functions:
Maintenance (alarms supervision).
Operations (like software upgrades, trouble shooting…).
Observations and statistics.
Subscriber management.
The 1300 XMC and the SDM use the CORBA or FTP protocol for control management.
9.8 INTERFACE BETWEEN 8650 SDM AND CCBS
The interface between the SDM and the Customer Care and Billing System (CCBS) enables opera-
tors to create, delete and modify subscribers in the Alcatel-Lucent 8650 SDM. Depending on net-
work architecture, the Alcatel-Lucent 8650 SDM can interface with the CCBS via SOAP CM, Corba
or Bulk XML for bulk management operations.

54/83
10 OPERATION AND MAINTENANCE
10.1 MANAGEMENT ARCHITECTURE
From the management point of view the 8650 SDM can be managed:
In local using a standard PC with a Web browser,
In remote via the 1300 XMC.
1300 XMC
Corba
Web CCBS
interface
based FTP
Corba,
8650 FTP
SDM
Web
interface
Local
Management
Figure 14. Management architecture
Man to machine interfaces are Web based interface: The user via a Web browse is able to manage
the Network Element.
Machine to machine interfaces are based on:
Corba IDL :
• Alarms interface,
• Observation interfaces.
• HW management,
• Logs management, …
SFTP:
• Software upgrade and backup /restore.
10.2 CENTRALISED OPERATION AND MANAGEMENT
The centralized management is performed by 1300 XMC (Cross-Domain and Maintenance Center).

55/83
The management system provides all the necessary function to manage in an efficient and user
friendly way the operator's network.
The 1300 XMC are connected to the equipment making Core Network through Element Manager
Layer (EML) application. These EML are supported by the equipment.
The 1300 XMC supports a comprehensive set of management functions permitting the operation
and maintenance of the entire network:
Management of network elements both on circuit and packet domains
Network topology with animated map,
Alarm collection and centralized alarm management
Centralized performance collection (observation counters and key performance indicators)
Centralized operators and profile management
Security management,
Event and logs management,
NE Software download and backup management for the whole network,
Interface to external OSS via open interfaces,
Network management level functions for packet and circuit domains
The 8650 SDM is connected to the 1300 XMC by Internet technology. Hence, the Data Communica-
tion Network (DCN) can be chosen in the full range of transport network of IP packets. Depending
on the applications, the communication between 1300 XMC and 8650 SDM can be:
SFTP, used for File Transfer (Software Downloading, Backup/Restore),
SSH, CORBA/IDL and WEB protocols, used for Applications management.
10.3 8650 SDM MANAGEMENT FUNCTION
SDM management function can be provided by platform or by application. These management

functions are described in next paragraphs.
10.3.1 PLATFORM MANAGEMENT
The Alcatel-Lucent ATCA platform offers a set of Operation and Maintenance features, which allows
an easy integration of the OAM of any application running on the platform. To achieve this goal,
OAM is organized to provide with a homogeneous view of every NE, whether or not inserted in a
managed network, and with OAM procedures common to the applications and the platform itself.
The platform and applications provides a set of web-based EML functions, with Graphical User In-
terface (GUI) and IDL interfaces compliant with Corba 2.3.The EML access can be performed either
locally through standard PC, either remotely through 1300 XMC.
Machine to machine interfaces are based on Corba methods.

56/83
The EML functions, described hereafter, are:
Platform services
• Hardware management,
• Software management,
• Access control,
• Observation management,
• Alarm management,
• Back up/Restore management,
• Command line and calendar,
• Log management,
• SS7 management,
AUC services
• AuC subscriber management
• Ciphering key management
HLR application management
• Application Context (AC) management,
• Subscriber data management,
• Translation management,
• Call trace management,
• Fraud prevention management,
• Supplementary services management,
• Operator Determined Barring (ODB) restriction management,
• Roaming restriction management,
• Subscriber-specific restriction management,
• Packet Data Protocol (PDP) context management,
• CAMEL subscription management,
• PLMN & countries management,
IMS HSS application management
• Subscriber private/public identities
• Public service identities
• User group Data
• Registration data set
• Service profile with initial Filter criteria
• Charging profile
• Roaming profile
• Opaque Data with application profile/service data
LTE application management

• Application Context (AC) management,
• Subscriber data management,
• Translation management,
• Fraud prevention management,
• Operator Determined Barring (ODB) restriction management,
• Roaming restriction management,
• Subscriber-specific restriction management,
• Packet Data Protocol (PDP) context management

57/83
MNP application
• Ported in /out subscribers
• Portability domain with routing number management
EIR application
• IMEI black/grey/white list management
• IMSI override management

58/83
11 ATCA PERFORMANCE
This section provides dimensioning information on 8650 SDM distributed configuration for stand-
alone application with ATCA V1 and ATCAV2 hardware configuration.
The CPU and memory are the two main resources considered in the dimensioning of the 8650 SDM
system. The application profiles and traffic model will drive usage of these resources for both
database and real-time resource usage. Capacity of the system is calculated with the load B traffic
that corresponds to the traffic input with an increase of 20% to cover peak situation.
Consequently, each application dimensioning result data provided in this section is based on a set
of input parameter including subscriber profile data and traffic model. Only application specific
data is provided in this section. Capacity results based on a mix of application can be provided on a
case by case based on customer request and input.
11.1 GSM/UMTS HLR CAPACITY
This section provides dimensioning information on 8650 SDM distributed configuration and com-
pact for stand-alone GSM/UMTS HLR application with ATCA V1 and ATCA V2 Hardware.
11.1.1 SYSTEM DIMENSIONING DATA
In order to guaranty a correct behavior of HLR system, Alcatel-Lucent has elaborated some system
dimensioning data. It has been established from system specifications, software constraints and op-
erator requests.
Values are valid in both GSM and UMTS environments unless otherwise specified.
Following table lists the main system dimensioning parameters.
Networks parameters Values

Maximum number of VLRs phase 1 which support phase 2 feature 200
Maximum number of roaming restriction lists in the HLR, each list hav- 120
ing between 1 and 60 addresses
Maximum number of GSM bearer capabilities 100
Maximum number of intra–PLMN entities for MAP version handling 1000
Maximum number of foreign addresses prefix for MAP version handling 1400
Number of SCCP translations 1400
HLR translator dimensioning values
Maximum number of translators that can be defined in the HLR 64
Maximum number of analysis units. Each unit allowing analysis of at 4000
least one digit

59/83
Maximum number of analysis results 2000
Data per subscriber
Maximum number of GGSN numbers per GPRS subscriber 32 / subscriber
Maximum number of roaming restriction lists per subscriber 60 for CS/subs. +
60 for PS/subs.
Maximum SMS center per subscriber 7 / subs.
Table 1: Common parameter values for the HLR/AuC
11.1.2 HLR/AUC CAPACITIES
The following table defines the subscriber profile values used to calculate the system capacity for
HLR/AuC application.
Subscriber data Profile Profile Profile

1 2 3
Mean number of MSISDN per subscriber 1 1 1,3
Percentage of Circuit-switch subscribers 100% 100% 100%
Percentage of Packet-switch (GPRS) subscribers 0% 100% 100%
Number of PDP Context per GPRS subscriber 1 3
Percentage of Camel subscribers 100% 100% 100 %
Percentage of Originating CSI among CAMEL subscribers 50% 100% 100%
Percentage of T-CSI among CAMEL subscribers 50% 50% 100%
Percentage of M-CSI among CAMEL subscribers 0 0 20%
Percentage of SS-CSI among CAMEL subscribers 0 0 20%
Percentage of U-CSI subscription per CAMEL subscribers 0 0 100%
Percentage of GPRS CSI among CAMEL subscribers 0 0 20%
Percentage of SMO-CSI among CAMEL subscribers 0 0 20%
Percentage of subscribers with Supplementary services 100% 100% 100%
Percentage of subscribers with General call services 100% 100% 100%
Average number of OSSS code per subscriber 16 16 16
Percentage of subscribers with Call Forwarding 0% 100% 100%
Average number of call forwarding per subscriber 0 1 3
Percentage of subscribers with Call Barring 0% 50% 100%
Percentage of activated Call Baring 0% 20% 100%
Percentage of subscribers with Call waiting 100% 100% 100%
Percentage of subscribers with Call tracing 0% 1% 1%
Percentage of subscribers with CUG 0% 2% 2%
Percentage of subscribers with LCS 0% 10% 10%
Table 2: HLR/AuC profile

60/83
With a standard BHCA of 1.55 BH/Subscriber at load B (mix of different HLR MAP messages)
and the profile previously defined is presented in the table below:
Configuration Profile 1 Profile 2 Profile 3

Small configuration ATCA V2 1. 57 MS 1. 56 MS 1. 53 MS
Small configuration ATCA V1 0.84 MS 0.83 MS 0.81 MS
Medium configuration ATCA V2 6.58 MS 6.45 MS 5.280 MS
Medium configuration ATCA V1 3.28 MS 2.92 MS 2.2 MS
Large Medium ATCA V1 8.19 MS 7.31MS 5.55 MS
Front End Medium ATCA V2 14.1 MS 14. 03 MS 13. 92 MS
Database Medium ATCA V2
12. 25 MS 11. 98 MS 11. 73 MS
Dynamic capacity
19. 6 MS 17. 54 MS 13.21 MS
Static capacity
Table 3: HLR/AuC capacity (MS = Million Subscribers)
11.2 IMS-HSS CAPACITY
This section provides dimensioning information on both 8650 SDM distributed and compact con-
figurations for stand-alone IMS-HSS application with ATCAV1 and ATCA V2 hardware con-
figuration.
The following table defines the subscriber profile values used to calculate the system capacity for IM-
HSS application.
Subscriber data Profile Profile 2

1
Number of PUID per IMS subscription 2 10
Subscriber AS per PUID 2 2
RD Per PUID 1 5
USP Specific IFC per PUID 4 3
Number of PrId per IMS subscription 1 4
Number of IRSET per subscription 2 5
Number of PUID-PRID MxN 1 1
Number of PRID-PUID MxN 2 10
Total Profile Length 4962 11078
Table 4: IM-HSS profile

61/83
For all the above assumptions, the following traffic mix is used with a default value of 2.35
BHCA/subs at load B:
Configuration Profile 1 Profile 2
Small configuration ATCA V2 0.55 MS 0.5 MS
Small configuration ATCA V1 0.3 MS 0.23 MS
Front-End Medium ATCA V2
5,01 MS 5.01 MS
Dynamic capacity
3.71 MS 2.48 MS
Dynamic capacity
5.54 MS 2.48 MS
Static capacity
Table 5: IM-HSS capacity (MS = Million IMS Subscribers)
11.3 EIR CAPACITY
figurations for stand-alone EIR application with ATCAV1 and ATCA V2 hardware con-figuration.
For all the above assumptions, the following traffic mix is used with a default value of 0,12
CheckIMEI per BH/ per subs in network at load B:
Configuration Capacity
Small configuration ATCA V2 46 MS
Medium configuration ATCA V2 50 MS
Front End Medium ATCA V2 169 MS
193 MS
Dynamic capacity
Table 6: EIR capacity (MS = Million Mobile Subscribers)
11.4 MNP CAPACITY
figurations for stand-alone EIR application with ATCAV1 and ATCA V2 hardware con-figuration.
For all the above assumptions, the following traffic mix is used with a default value of 0,6 MNP
access per BH/ per subs in network at load B:

62/83
Configuration Capacity
Small configuration ATCA V1 5,3 MS
Front End Medium ATCA V2 83 MS
128 MS
Dynamic capacity
Table 7: MNP capacity (MS = Million Mobile Subscribers)
11.5 PROVISIONING CAPACITY
Type of operation performed and size of the data/profile manipulated in this operation influence
provisioning performance. For a given operation and given profile the performance on compact
configuration is fixed, whereas on distributed configuration the provisioning capacity grows as the
system scale as each FE hosts provisioning capability.
This implies that provisioning capability with for example a deployment of 4 + K Front-End Nodes
allows 4 times the capacity of FE per BH as K is considered only for support of geographical redun-
dancy.
Type of operation in BH Compact V2 FE V2 3
Creation of HLR Subscriber profile1 120K/BH 100K/BH
Modification of HLR Subscriber profile1 400K/BH 320K/BH
Deletion of HLR Subscriber profile1 250 K/BH 200K/BH
Creation of HSS Subscriber profile1 60K/BH 50K/BH
Modification of HSS Subscriber profile1 140K/BH 100K/BH
Deletion of HSS Subscriber profile1 90K/BH 70K/BH
Table 8: Provisioning Capability
11.6 8650 SDM SN7 CONNECTIVITY
The table hereafter gives the SN7 connectivity
3 Performance considered is with no latency between FE and BE

63/83
SN7 connectivity Compact Small Compact Medium FE HLR
Configuration Configuration
Medium
Maximum of SN7 signalling link 124 620 1240
Maximum number of E1 (64 Kbits or HSL 2Mb)4 4 20 40
Maximum SCTP connection for SIGTRAN 1024 2048 2048
Table 9: SS7 connectivity
4 E1 links are available per SS7 AMC on a Real Time station of a Front End.
SIGTRAN connectivity can also be provided simultaneously with SS7 connectivity.
4It is possible to mix 64 Kbits links and HSL links in the same Front End. However in the configuration. All the links of one Real Time
station must be identical : either 64 Kbits or HSL (2 Mbits).

64/83
12 ATCA V2 TECHNICAL CHARACTERISTICS
This chapter describes the specific technical characteristics of the 8650 SDM for ATCAV2 Hardware.
12.1 PHYSICAL DIMENSIONS
The rack for SDM is a 19" cabinet

• Width: 600 mm
• Depth: 600 mm
• Height: 2125 mm, 44U useful + base 100 mm
The cabinet weight fully equipped is less than 400 kg.
The ATCA chassis dimension are:
• 11U (Height)
• 19 inches (Width)
• 450 mm (Depth).
1U or 2U air flow deflectors are added at the bottom and at the top of each ATCA chassis.
12.2 SPACE REQUIREMENTS
The placement of each device takes into account mainly the absolute temperature rate, the weight
and airflow for the cooling of each device. In some case, depth, power dissipation, easy wiring is
also taken into account.
Each rack must be installed in a stand-alone mode (600mm overall width). For thermal reasons, it is
not possible to join several racks together and mounting only a side panel.
To exit of the housing, the links must go through the housing on the top or on the bottom of the
rack. To standardize the length of the cords, all racks series must be installed in field, in stand-alone
mode (Figure 1).
598 mm
NRA2xx NRA2xx
600 mm
Figure 1: Location of the racks in field in stand-alone mode

65/83
12.3 CONSUMPTION
The following table provides the maximum power consumption for mandatory and optional ele-
ments:
Maximum Power Consumption Small Medium DB Node FE Node

Conf Conf Medium Medium
ATCA rack (DC 48 V) 1180 W 1645 W 1645 W 1 645 W
Optional Alcatel-Lucent 120 W 120 W 120 W 120 W
Routers bundle (DC 48 V)
12.4 ENVIRONMENTAL CONDITIONS
8650 SDM complies with environmental condition standards described in Table 10:
Field Comment
EMC Compliance with EN 300 386 (Public Telecommunication Network
Equipment, ElectroMagnetic Compatibility (EMC) requirements.)
Compliance with IEC 61000-4 (-2 Electrostatic discharges, -3 Radiated
field, -4 Electrical Fast Transient, -5 Lightning surges, -6 Conducted RF
signal)
Compliance With NEBS GR1089
Safety Compliance with EN 60950 (Safety of information technology
equipment)
Network Attachment Compliance with:
. ITU G.957 (Optical STM-N)
. G.703 (T1/E1/155Mbps)
. G.707 (Synchronization Status) Network node interface for the synchronous
digital hierarchy (SDH)
. G.823 Jitter/Wander, Digital networks 2048 kbit/s
. G.825 Jitter/Wander, Digital networks for Synchronous Digital Hierarchy
(SDH)
. G.957 Optical Interfaces, Digital networks for Synchronous Digital Hierarchy
(SDH)
. G.813 Digital transmission systems - Digital networks
Power and Grounding EN 300 132-2 (Equipment engineering; Power supply interface at the
requirements input to telecommunication equipment. Part 2 Operated by direct
current (d.c.) sources)

66/83
EN 300 253 (Earthing and bonding configuration inside
telecommunications centers)
Climatic and EN 300 019-2-3 (Operating: T3.1/T3.1 E), EN 300 019-2-1 (Storage:
Mechanical T1.1), EN 300 019-2-2 (Transport: T2.2)
Fire-resistance Compliance with Bellcore GR-63-CORE, Sections 4.2 and 5.2
Earthquake protection Compliance with NEBS GR-63-Core-2006 as defined in chapter 4.4.1
Environmental Compliance RoHS, and WEEE (eco declaration)
Acoustics Compliance with EN 300 753 Class 3.1 (1997)
Table 10: Environmental conditions compliance
12.5 POWER SUPPLIES AND CABLING
This chapter provides information on power requirements. This includes:

• standard and emergency lighting,
• DC power supply,
• Secured DC power supply,
• Grounding requirements.
12.5.1 LIGHTING AND POWER OUTLETS
The 8650 SDM is powered with DC operating Voltage range –40Vdc to –75Vdc with nominated
rated voltage –48Vdc / -60Vdc.
Telecommunications platforms can require:
• Digital Distribution Frame (DDF),
• Optical Distribution Frame (ODF),
• Cables and cable trays.
Note: The electrical power sources can be divided into two categories:
• secured,
• uninterruptible.
Secured sources can resist simple power failures by including a secondary backup source such as a
generator. This means that a short power cut will occur during any switchover period.
Uninterruptible sources are used to remove the possibility of micro cuts by the inline use of batteries.

67/83
Lighting
Lighting must be by instant-start fluorescent tubes that meet the technical specifications currently
required in electronic equipment rooms.
If there is... Then the lighting fixture should be ...

A suspended ceiling Recessed or surface mounted.
No suspended ceiling Suspended from the ceiling at approximately 3 m above the

floor, which allows for the 500 mm minimum clearance re-
quirement.
The light fixtures are placed in line and parallel with the equipment racks, so that the minimum light-
ing level is 350 lx one meter above the floor. The fixtures must be:
• 650 mm from the front of the racks,
• 650 mm from the rear of the racks.
Emergency lighting must meet local safety standards.
Power Circuit Integrity

The lighting equipment and power outlets in the equipment room are powered separately from the
general electrical supply of the building.
Notice
Prepare power distribution before installation
Light fixtures and power outlets must be fitted and connected to the low voltage electrical system
before installing the system.
12.5.2 POWER REQUIREMENTS AND SECURITY
The power should be supplied from a secured power plant. The power provided must be:
• Stable,
• Resistant to simple failures.
Different circuits can be used for the peripheral equipment used on the same platform. Printers and
access terminals may not require the same quality of security as the network elements.
The on-site telecommunications network can require:
• 48 V DC for telecommunications components,
To secure the system, at least two separate DC voltage circuits are used. The Alcatel-Lucent Modular
Power Supply Station (SAM) is a complete power plant housed in a single rack. It produces from the
AC main supply:

68/83
• Stable rectified 48 V DC,
• Stable rectified 230 V AC.
12.5.2.1 DC POWER
Historically, countries have developed different safety regulations concerning the direct current that
can be safely handled by personnel. France, for example, uses 50 volts as a maximum voltage.
Other countries can accept slightly higher voltages.
Due to these differences, Alcatel-Lucent produces equipment that can operate within the interna-
tional standards range: 40.5 V to 72.0 V. Direct current is generally produced on the platform for
48 V or 60 V.
This can be provided by the operator or by Alcatel-Lucent.
Alcatel-Lucent proposes a SDE (energy distribution) rack to supply the 8650 SDM from the customer
power supply facilities. Other supply configurations are possible, and can be optionally proposed
according to the customer site requirements.
12.5.3 CABLING
All cable connections must be in accordance with local regulation rules. To ensure good behavior of
the system, power cables and signaling cables must be clearly separated. All power cables (230V
and 48V) are run in cable trays under the raised floor or overhead.
12.5.4 GROUNDING REQUIREMENTS
In order to guaranty personnel safety, the earth resistance value of the building and the connection
of the equipment to the earth must be in accordance with local regulation rules.
The equipment has been designed to be implemented in CBN networks. Nevertheless, it can be also
implemented in IBN networks with additional mounting kit.
The electrical and mechanical ground of the equipment is connected to the Meshed Bonding Net-
work. The ETSI standard document (EN 300 253) defines detailed requirements concerning Mesh
Bounding Network and CBN. The connection for each rack of the system to the Mesh bonding Net-
work requires to be less than < 20cm and must be made with a tinned copper braid.
With raised floor, the Meshed Bounding Network must be electrically connected to the metallic part
of the raised floor. The transverse resistance of the raised floor is between105 Ω and 108 Ω which
respects the Conference of European Posts and Telecommunications (CEPT) Recommendation T/TR-
02-08 (1986) on the conductivity of floors in telephone exchanges.

69/83
12.5.5 POWER GENERATORS
Depending on the geographical situation of the site, electric power is obtained through the national
grid system or generated locally. In all cases, emergency backup supplies should be available.
All the DC elements are covered temporarily by batteries. Emergency lighting must be automatic for
all the entrances and passages.
These systems should be tested periodically (when possible) to ensure the continuity of service.

70/83
13 ATCA V1 TECHNICAL CHARACTERISTICS
This chapter describes the specific technical characteristics of the 8650 SDM for ATCA V1 Hardware.
13.1 PHYSICAL DIMENSIONS
The rack for SDM is a 19" cabinet

• Width : 600 mm
• Depth : 800 mm
• Height : 2000 mm, 42U useful + base 100 mm
The ATCA subrack dimension is 13 U (Height) * 19 inches (Width) * 600 mm (Depth).
The cabinet weight fully equipped is 350 kg.
13.2 SPACE REQUIREMENTS
The placement of each device takes into account mainly the absolute temperature rate, the weight
and airflow for the cooling of each device. In some case, depth, power dissipation, easy wiring are
also taken into account.
Each rack must be installed in a stand-alone mode (592mm overall width). For thermal reasons, it is
not possible to join several racks together and mounting only a side panel.
To exit of the housing, the links must go through the housing on the top or on the bottom of the
rack. To standardize the length of the cords, all AS01 racks series must be installed in field, in
stand-alone mode (Figure 1).
Figure 2: Location of the racks in field in stand-alone mode

71/83
13.3 CONSUMPTION
The following table provides the maximum power consumption for mandatory and optional ele-
ments:
Maximum power consumption Small Medium Large

ATCA rack (DC 48 V) 650 W 1030 W 2030 W
Optional Alcatel-Lucent 120 W 120 W 120 W
routers (DC 48 V)
13.4 ENVIRONMENTAL CONDITIONS
1430 complies with environmental condition standards described in Table 10:
Field Comment
EMC Compliance with EN 300 386 (Public Telecommunication Network
Equipment, ElectroMagnetic Compatibility (EMC) requirements.)
Compliance with IEC 61000-4 (-2 Electrostatic discharges, -3 Radiated
field, -4 Electrical Fast Transient, -5 Lightning surges, -6 Conducted RF
signal)
Safety Compliance with EN 60950 (Safety of information technology
equipment)
Network Attachment Compliance with :
. ITU G.957 (Optical STM-N)
. G.703 (T1/E1/155Mbps)
. G.707 (Synchronization Status) Network node interface for the synchronous
digital hierarchy (SDH)
. G.823 Jitter/Wander, Digital networks 2048 kbit/s
. G.825 Jitter/Wander, Digital networks for Synchronous Digital Hierarchy
(SDH)
. G.957 Optical Interfaces, Digital networks for Synchronous Digital Hierarchy
(SDH)
. G.813 Digital transmission systems - Digital networks
Power and Grounding ETS 300 132-2 (Equipment engineering; Power supply interface at the
requirements input to telecommunication equipment. Part 2 Operated by direct
current (d.c.) sources)
ETS 300 253 (Earthing and bonding configuration inside
telecommunications centers)
Climatic and ETS 300 019-2-3 (Operating), ETS 300 019-2-1 (Storage), ETS 300

72/83
Mechanical 019-2-2 (Transport)
Fire-resistance Compliance with Bellcore GR-63-CORE, Sections 4.2 and 5.2
Earthquake protection Compliance with NEBS GR-63-Core-2002 as defined in chapter 4.4.1
Acoustics Compliance with ETS 300 753 Class 3.1 (1997)
Table 11: Environmental conditions compliance
13.5 POWER SUPPLIES AND CABLING
This chapter provides information on power requirements. This includes:

• standard and emergency lighting,
• AC power supply,
• secured AC power supply,
• DC power supply options,
• grounding requirements.
13.5.1 LIGHTING AND POWER OUTLETS
Telecommunications platforms can require:

• 380/230 V Alternating Current (AC) power box,
• 48 V and/or 60 V Direct Current (DC) power box,
• Digital Distribution Frame (DDF),
• Optical Distribution Frame (ODF),
• cables and cable trays.
Note: The electrical power sources can be divided into two categories:
• secured,
• uninterruptible.
Secured sources can resist simple power failures by including a secondary backup source such as a
generator. This means that a short power cut will occur during any switchover period.
Uninterruptible sources are used to remove the possibility of microcuts by the inline use of batteries.
The DC voltage from the batteries is used to produce the required AC voltage for any 220V-240V
network elements.

73/83
Lighting
Lighting must be by instant-start fluorescent tubes that meet the technical specifications currently
required in electronic equipment rooms.
If there is... then the lighting fixture should be ...

A suspended ceiling Recessed or surface mounted.
No suspended ceiling Suspended from the ceiling at approximately 3 m above the

floor, which allows for the 500 mm minimum clearance re-
quirement.
The light fixtures are placed in line and parallel with the equipment racks, so that the minimum light-
ing level is 350 lx one meter above the floor. The fixtures must be:
• 600 mm from the front of the racks,
• 600 mm from the rear of the racks.
Emergency lighting must meet local safety standards.
Power Circuit Integrity

The lighting equipment and power outlets in the equipment room are powered separately from the
general electrical supply of the building.
Notice
Prepare power distribution before installation
Light fixtures and power outlets must be fitted and connected to the low voltage electrical system
before installing the system.
13.5.2 POWER REQUIREMENTS AND SECURITY
The power should be supplied from a secured power plant. The power provided must be:
• stable,
• resistant to simple failures.
Different circuits can be used for the peripheral equipment used on the same platform. Printers and
access terminals may not require the same quality of security as the network elements.
The on-site telecommunications network can require:
• 220-240 V, 50 Hz AC power for the terminals, printers and PC,
• 48 V and 60 V DC can be converted to 220-240 V AC power in the telecommunications
racks as required by the different components.

74/83
To secure the system, at least two separate DC voltage circuits are used. The Alcatel-Lucent Modular
Power Supply Station (SAM) is a complete power plant housed in a single rack. It produces from the
AC main supply:
• stable rectified 48 V DC,
• stable rectified 230 V AC.
13.5.2.1 AC POWER
The telecommunications racks are equipped with two extension leads called IDCEM. Each IDCEM
provides 8 x 230 V AC. Both IDCEMs must be protected by a 6 A or 8 A circuit breaker upstream,
outside of the rack. On each distribution frame, the maximum power distribution per subrack is
1100 W.
Attention
Provide Circuit Breakers
If circuit breakers are not provided in the rack, the installation engineer must provide circuit breakers
upstream.
13.5.2.2 DC POWER
Historically, countries have developed different safety regulations concerning the direct current that
can be safely handled by personnel. France, for example, uses 50 volts as a maximum voltage.
Other countries can accept slightly higher voltages.
Due to these differences, Alcatel-Lucent produces equipment that can operate within the interna-
tional standards range: 40.5 V to 72.0 V. Direct current is generally produced on the platform for
48 V or 60 V.
This can be provided by the operator or by Alcatel-Lucent.
Alcatel-Lucent proposes a SDE (energy distribution) rack to supply the HLR from the customer power
supply facilities. Other supply configurations are possible, and can be optionally proposed accord-
ing to the customer site requirements.
13.5.3 CABLING
All cable connections must be in accordance with applicable standards. All cable fields must be con-
nected to the racks at the cable ground sealing boxes. All cables (230V and 48V) are factory-made,
shielded and are run in cable trays under the raised floor or overhead.
13.5.4 GROUNDING REQUIREMENTS
Raised floor grounding

The raised floor is grounded by a Meshed Bonding Network. All associated equipment frames and
racks and usually the DC power return conductor, are bonded together. This is done at multiple
points to the main grounding and bonding system of the telecommunication building.
A 5mm2 section of flexible, tinned, copper braid is attached at 1.20 m intervals in both directions
(every other jack). This means that each tile is resting on at least one grounded jack.

75/83
The two flexible braids forming the intersection of the Meshed Bonding Network are linked to jacks
at the bottom by screw-clamped collars. The flexible braids run along the floor and are not raised so
that they will not be pulled loose inadvertently. Each flexible braid built into the bonding network
forms a continuous strip. The vertical runs at both ends of the braid, which pass through the floor,
are connected to the bonding ring.
The transverse resistance of the raised floor is between105 Ω and 108 Ω which respects the Confer-
ence of European Posts and Telecommunications (CEPT) Recommendation T/TR-02-08 (1986) on
the conductivity of floors in telephone exchanges.
For detailed information on bonding and grounding, see the ETSI standard document: ETS 300
253.
The maximum resistance allowed for the earth connection must be less than 3 Ω.
13.5.5 POWER GENERATORS
Depending on the geographical situation of the site, electric power is obtained through the national
grid system or generated locally. In all cases, emergency backup supplies should be available.
All the DC elements are covered temporarily by batteries. Emergency lighting must be automatic for
all the entrances and passages.
These systems should be tested periodically (when possible) to ensure the continuity of service.

76/83
GLOSSARY
A
AAA Authentication/Authorization/Accounting
AC Alternating Current
ACID Atomicity Coherency Isolation Duration
AD Activity Domain
AKA Authentication and Key Agreement
ALMAP Alcatel-Lucent Management Platform
ALR Active Location Retrieval
AOC Advice Of Charge
API Application Interface
AS Application Server
ASP Application Software Package
ATCA Advanced Telecom Computing Architecture
ATI Any Time Interrogation
AuC Authentication Center
AUTN AUthentication TokeN
AVP Attribute Value Pair
B
BEP Back End Processor
BSS Billing Support System
BSF Bootstrapping Server Function (IMS)
C
CAMEL Customized Applications for Mobile network Enhanced Logic
CB Call Barring
CBN Common Bonding Network
CCBS Customer Care and Billing System
CF Call Forwarding
CHAP Challenge Handshake Authentication Protocol
CK Ciphering Key
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction

77/83
COLP Connected Line Identification Presentation
COLR Connected Line Identification Restriction
CORBA Common Object Request Broker Architecture
CSCF Call Connectivity Session Control Function
CSCN Circuit-Switched Core Network
Cx 3GPP Standards Reference Point between HSS & CSCF
CU Computer Unit
CUG Closed User Group
CW Call Waiting
D
DB Database
DBMS Database Management System
DC Direct Current
DCN Data Communication Network
DDF Digital Distribution Frame
DHCP Dynamic Host Configuration Protocol
DNS Domain Name Server
Dx/Dh 3GPP Standard Reference Points between SLF & CSCF/IMS-AS
E
EAP Extensible Authentication Protocol
ECT Explicit Call Transfer
EIR Equipment Identity Register
EMC Electro Magnetic Compatibility
EML Element Manager Layer
ETSI European Telecommunications Standards Institute
F
FCS Fixed Cellular Subscribers
FEP Front End Processor
FPLMN Foreign Public Land Mobile Network
FTP File Transfer Protocol
G
GAN Generic Access Network
GANC Generic Access Network Controller
GGSN Gateway GPRS Support Node

78/83
GMLC Gateway Mobile Location Center
GMSC Gateway MSC
GPRS General Packet Radio Service
GSM Global System for Mobile communications
GUI Graphical User Interface
H
HLR Home Location Register
HMI Human Machine Interface
HOLD Call Hold
HPD Home Profile Database
HPLMN Home Public Land Mobile Network
HSL High Speed Link
HSS Home Subscriber Server
HTML Hyper Text Management Language
I
IBN Isolated Bonding Network
I-CSCF Interrogating Call Connectivity Session Control Function
IDL Interface Definition Language
IK Integrity Key
IMS HSS IP Multimedia Subsystem Home Subscriber Server
IMS IP Multimedia Subsystem
IMS-A IP Multimedia Subsystem Authentication
IMSI International Mobile Subscriber Identity
IN Intelligent Network
IP Internet Protocol
ISIM Internet Subscriber Identity Module
K
K authentication Key (UMTS)
Kc ciphering Key
Ki individual authentication Key (GSM)
L
LCS LoCation Service

79/83
LDAP Lightweight Directory Access Protocol
M
MAP Mobile Application Part
MCI Malicious Call Identification
MMC Man Machine Command
MMS MultiMedia Messaging
MNP Mobile Number Portability
MPC Multiple Point Code
MSC Mobile services Switching Center
MSIN Mobile Subscriber Identification Number
MSISDN Mobile Subscriber ISDN Number
MSRN Mobile Station Roaming Number
MSU MeSsage Unit
MT-LR Mobile Terminating-Location Report
MTPY MulTiPartY
MWD Message Waiting Data
M3UA MTP3 User Adaptation Layer
N
NAI Network Access Identifier

NDC National Destination Code
NE Network Element
NMC Network Management Center
NPDB National Portability DataBase
O
OAM Operation And Maintenance
ODB Operator Determined Barring
ODF Optical Distribution Frame
OPC Originating Point Code
OS Operating System
OSS Operational support system
OSSS Operator-Specific Supplementary Service
P

80/83
PCI Peripheral Component Interconnect
P-CSCF Proxy Call Connectivity Session Control Function
PDN Packet Data Network
PDP Packet Data Protocol
PDU Packet Data Unit
PMC PCI Mezzanine Card
PMD PostMortem Dump
PSCN Packet Switch Core Network
PSU Power SUpply
R
RADIUS Remote Authentication Dial-In User Service
RAM Random Access Memory
RAN Radio Access Network
RAND RANDom number
RNC Radio Network Controller
RPM Redhat Package Manager
RSZI Regional Subscription Zone Identity
RT Real Time
S
SAC Service Area Code
SAI Service Area Identifier
SAM Modular Power Supply Station
SC Service Center
SCIM Software Component Instance Materialization
SCP Service Control Point
S-CSCF Serving Call Connectivity Session Control Function
SCTP Stream Control Transmission Protocol
SDM Subscriber Data Manager
SGSN Serving GPRS Support Node
SIGTRAN Signaling Transport
Sh 3GPP Standards Reference Point between HSS & IMS-AS
SIM Subscriber Identity Module
SIP Session Initiation Protocol

81/83
SLF Subscription (Subscriber) Locator Function
SMPP Short Message Peer to Peer Protocol
SMS Short Message Service
SMS-MT Short Message Service-Mobile Terminated
SMS-C Short Message Service- Center
SN Subscriber Number
SOAP Simple Object Access Protocol
SOR Support Optimal Routing
SPD Serving Profile Database
SQL Structured Query Language
SRES Signed RESponse
SRF Specialized Resource Function
SS Nº7 Signaling System Nº7
SUPASP SUPervisor Application Software Package
T
U
UE User Equipment
UICC User IndentifiCation Card
UMA Unlicensed Mobile Access
UNC UMA Network Controller
UMTS Universal Mobile Telecommunications System
URL Unique Resource Locator
USIM Universal Subscriber Identity Module
USSD Unstructured Supplementary Service Data
V
VLR Visitor Location Register
VMSC Visited MSC
VSA Vendor Specific Attribute
W
WAC WIMAX Access Controller
WAN Wide Area Network
WiMAX Worldwide Interoperability for MicroWave Access

82/83
WLAN Wireless Local Area Network
X
XML eXtensible Markup Language
XMC Cross-Domain and Maintenance Center
XRES eXpected RESponse
Z
Zh 3GPP Standards Reference Point between HSS & BSF
0-1
3GPP Third Generation Partnership Project

83/83

Alcatel-Lucent - 8650 SDM R3.1 Product Description PDF

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Alcatel-Lucent - 8650 SDM R3.1 Product Description PDF

Загружено:

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

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

ALCATEL-LUCENT 8650 SDM SOLUTION

8650 SUBSCRIBER DATA MANAGER

8650 SDM - PRODUCT DESCRIPTION

4 KEY BENEFITS OF THE ALCATEL-LUCENT 8650 SDM SOLUTION ....................................................12

5 PLATFORM ARCHITECTURE ..............................................................................................................17

6 SOFTWARE ARCHITECTURE & DEFENSE MECHANISMS ..................................................................26

7 SDM APPLICATION OVERVIEW DESCRIPTION .................................................................................35

8650 SDM - PRODUCT DESCRIPTION

8 SUBSCRIBER ADMINISTRATION .......................................................................................................46

9 INTERFACES AND PROTOCOLS .......................................................................................................48

10 OPERATION AND MAINTENANCE...................................................................................................55

11 ATCA PERFORMANCE ......................................................................................................................59

8650 SDM - PRODUCT DESCRIPTION

12 ATCA V2 TECHNICAL CHARACTERISTICS ........................................................................................65

13 ATCA V1 TECHNICAL CHARACTERISTICS ........................................................................................71

8650 SDM - PRODUCT DESCRIPTION

Table 1: Common parameter values for the HLR/AuC.................................................................60

8650 SDM - PRODUCT DESCRIPTION

IMS solution with IMS HSS application

LTE Solution with LTE application (3GPP HSS).

8650 SDM - PRODUCT DESCRIPTION

Or a mix of any applications available on the Alcatel-Lucent 8650 SDM portfolio.

The Alcatel-Lucent 8650 SDM can be deployed in 2 network configurations:

8650 SDM - PRODUCT DESCRIPTION

WiMAX SDM SIP

GPRS IP Packet Data

Figure 1. Network architecture with Compact architecture

8650 SDM - PRODUCT DESCRIPTION

Figure 2. Network architecture with Distributed configuration

8650 SDM - PRODUCT DESCRIPTION

3.1 MAIN MARKET CHALLENGES

• Capacity (virtually unlimited) • Provisioning

• Data availability and security • Open system/platform

8650 SDM - PRODUCT DESCRIPTION

High capacity in a reduced footprint

High degree of availability

Flexible redundancy schemes

IP Connectivity (management and signaling with SIGTRAN capabilities)

High speed links

Standard and open interfaces (IP, SOAP, Corba)

8650 SDM - PRODUCT DESCRIPTION

One open and standard IT platform

High capacity & scalability in small footprint

Solution with very high capacity (with distributed configuration),

Smooth evolution from compact to distributed configuration

A small footprint cabinet (19"),

And minimized power consumption.

Alcatel-Lucent solution based flexible platform:

IMS HSS application,

Mobile Number Portability Database (MNP-SRF)

Equipment Identity Register (EIR)

Open Data Storage Server

Highly flexible & efficient provisioning

8650 SDM - PRODUCT DESCRIPTION

Field proven solution

8650 SDM - PRODUCT DESCRIPTION

GPRS handling: managed on a subscribers basis.

Multi country handling: to manage several Countries in the same SDM.

MAP screening feature for advanced routing scenario

Management of IMSI Signalling without using MSISDN

8650 SDM - PRODUCT DESCRIPTION

Following are the main features proposed in HSS application:

Full Sh Compliance (UDR/A, PUR/A, SNR/A, PNR/A)