One-NDS 8.

0 System Architecture

One-NDS 8.0 System Architecture

Content
One-NDS 8.0 System Architecture 1
1 Introduction 3
1.1 About that document 4
1.2 General 5
1.3 Products and Systems 9
2 One-NDS Functionality 11
2.1 Functional Components of One-NDS 12
3 One-NDS - An X.500-Based Directory 17
3.1 General 18
3.2 The Directory 20
3.3 Distribution of data 22
3.4 Directory Service 24
3.5 In-memory database 26
3.6 Summary 28

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
1
 One-NDS 8.0 System Architecture

CN65301EN86GLA0
2 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

1 Introduction

One-NDS 8.0 System Architecture

Introduction

Fig. 1

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
3
 One-NDS 8.0 System Architecture

1.1 About that document

A service pack (SP) is an orderable or downloadable update to a customer's software
that fixes existing problems and, in some cases, delivers product enhancements.
One-NDS was delivered in the beginning with SP1, later SP2, SP3 and SP4 followed.
The service packs issued after SP4 are called extension packages (EP).
This document covers all course relevant customer features concerning EP6.

CN65301EN86GLA0
4 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

1.2 General
One Network Directory Server (One-NDS) is a subscriber data management solution
that unifies subscriber data by storing it in a single centralized repository and enables
applications to share the data for a common, consistent view. The solution is suitable
for deployment in either fixed or mobile networks. One-NDS has identical functionality
and components for all possible applications, including different types of application
servers such as Home Location Register (HLR), Home Subscriber Server (HSS),
Authentication, Authorization, and Accounting (AAA), Equipment Identity Register
(EIR), Mobile Number Portability (MNP) server, and others. To provide high
performance that is suitable for telecommunications environments, One-NDS uses
entirely in-memory data storage and is optimized for high transactional throughput
and low directory latency.
One-NDS stores subscriber, service, network, and application configuration data.
Subscription and service data located within the directory is made available to
mobile, fixed, or converged network operators so that they can query the data and
update all applications in a controlled and secure manner. The separation of
subscriber data from the application server, the provisioning of an open external
interface to this data, and the extensibility of the data model lead to rapid
development of innovative services, easier application integration, and significantly
improved resilience and scalability.
Data provisioning defines the management of subscriber-specific data within the
network. To manage subscriber data, the SPML/SOAP/HTTP interface of One-NDS
can be integrated into any operator management system or operator Web portal to
allow operators access to selected subscriber data, such as user IDs and service
parameters.
In addition to read/write access to subscriber data, this interface also provides access
to the HTTP digest password, thus enabling the Web portal to authenticate the
subscriber.

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
5
 One-NDS 8.0 System Architecture

MSC/VLR SGSN MMSC

Network Layer

IP network / SS7 network

Service Layer
(dataless)
HLR HSS EIR

Data Layer
One-NDS

Fig. 2 One-NDS in the Network

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CN65301EN86GLA0
. . . . .
© 2012 Nokia Siemens Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One-NDS 8.0 System Architecture

1.2.1 Service Layer

HLR
The HLR acts as a Home Location Register (HLR) and an Authentication Center
(AuC) in the network. These combined entities perform the following functions in the
network:
 Authenticating subscribers when they register on the network.
 Store subscriber details including locations and services.
 Access point for subscriber details in the network

EIR
The equipment identity register keeps a list of mobile phones (identified by their IMEI)
that are to be monitored or banned from the network. This is designed to track stolen
mobile phones. In theory, all data about stolen mobile phones should be distributed
to all EIRs in the world through a Central EIR. The EIR data does not have to change
in real time, which means that this function can be less distributed than the HLR
function.
The EIR is a database that contains information about the identity of the mobile
equipment that prevents calls from stolen, unauthorized, or defective mobile stations.

PCS
Policy control is used to authorize and control the network resource usage by
subscribers. It also prevents the misuse of network quality of service (QoS), and
enables the operator to limit the resource usage. Policy control ensures that services,
for example voice over IP, video over IP, file transfer, and conferencing, can be
offered with guaranteed QoS for high quality user experience.

HSS
The Home Subscriber Service (HSS) is defined by the 3GPP standards as HLR, AuC
and IMS implementation in the network. The HSS provides the HLR functions in the
IMS Domain. This includes:
 Authenticating subscribers when they register on the network.
 Store subscriber details including locations and services.
 Access point for subscriber details in the network
 Support for the above functions in the Core network and the IMS domain (for IP
multimedia applications).
The IMS (IP Multimedia Subsystem) enables the support for IP multimedia
applications within the UMTS system, thus enabling PLMN operators to offer their
subscribers multimedia services based on and built upon Internet applications,
services and protocols.
It can be implemented as an extension to the HLR or as an extension to an already
existing HLR.

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
7
 One-NDS 8.0 System Architecture

MNP
Mobile number portability (MNP) is a facility that allows subscribers to retain their
number when moving location, changing carrier or changing operator. The MSC
forwards the request to the MNP if the HLR could not find it. The MNP will search for
the number and if it is for another network will add a routing prefix to the MSISDN
and forward it on to the foreign network.

1.2.2 Network Layer

MSC/VLR
The MSC performs the switching functions of the mobile network. It also provides
connection to other networks. The VLR contains information from a subscriber's HLR
necessary to provide the subscribed services to visiting users. When a subscriber
enters the covering area of a new MSC, the VLR associated to this MSC will request
information about the new subscriber to its corresponding HLR. The VLR will then
have enough data to assure the subscribed services without needing to ask the HLR
each time a communication is established. The VLR is always implemented together
with a MSC; thus, the area under control of the MSC is also the area under control of
the VLR

SGSN
The general packet radio services (GPRS) system is used by GSM mobile phones for
transmitting IP packets.
A serving GPRS support node (SGSN) is responsible for the delivery of data packets
from and to the mobile stations within its geographical service area. Its tasks include
packet routing and transfer, mobility management (attach/detach and location
management), logical link management, and authentication and charging functions.
MMSC
The Multimedia Messaging Service Center (MMSC) is the store and forward network
element that delivers the MMS messages from the sender to the recipient. The
MMSC concept is similar to an SMSC, that is, the server stores the message only for
the time required to find the receiving device. After the receiving device is found, the
MMSC immediately forwards the MMS message to the recipient and the message is
deleted from the MMSC. Thus, the MMSC is not a mailbox server, because it does
not store the message if the message can be delivered to the recipient device.

SMSC
An SMS center (SMSC) is responsible for handling the SMS (Short Message
Service) operations of a wireless network. When an SMS message is sent from a
mobile phone, it will reach an SMS center first. The SMS center then forwards the
SMS message towards the destination. An SMS message may need to pass through
more than one network entity (e.g. SMSC and SMS gateway) before reaching the
destination. The main duty of an SMSC is to route SMS messages and regulate the
process. If the recipient is unavailable (for example, when the mobile phone is
switched off), the SMSC will store the SMS message. It will forward the SMS
message when the recipient is available.

CN65301EN86GLA0
8 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

1.3 Products and Systems

One-NDS Directory, together with multiple application clients, builds up a distributed
directory network element function. This occurs by distributing access through any
application server to all subscriptions (subscriber data) stored in One-NDS. Each
application server connects to the One-NDS Directory for data access and update
notifications. A big advantage is the modularity of the products to build a system for
the customer according his needs. Products are e.g.
 One-NDS
 One-AAA FE
 One-EIR FE
 One-MNP FE
 NT HLR FE
 NT HSS FE
 DX HLR FE
 PCS

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
9
 One-NDS 8.0 System Architecture

One-AAA System One-EIR System One-MNP System NT HLR System NT HSS System DX HLR System

One-AAA FE One-EIR FE One-MNP FE NT HLR FE NT HSS FE DX HLR FE

One-NDS

Fig. 3 Systems and Products

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CN65301EN86GLA0
. . . . .
© 2012 Nokia Siemens Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One-NDS 8.0 System Architecture

2 One-NDS Functionality

One-NDS 8.0 System Architecture

One-NDS Functionality

Fig. 4

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
11
 One-NDS 8.0 System Architecture

2.1 Functional Components of One-NDS

The main functional components of One-NDS are illustrated on the next page:
Beginning with EP5, the following server types are supported along with the current
released hardware platform:
 Sun Netra X4270
 Fujitsu Primergy RX200 S6
 IBM Bladecenter HS22

The following hardware components are also supported:

 300 GB HDD
 SUN Netra x42 with 64 GB memory
 Mixed SUN/Fujitsu hardware configuration within a system is released

CN65301EN86GLA0
12 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

components NDS PGW NTF ADM INS SM

SuSe Linux Enterprise Edition

platform

Sun Netra X4200 / Fujitsu Primergy / IBM Bladecenter

NDS=Network Directory Server

PGW=Provisioning Gateway
NTF=Notification Manager
ADM=One-NDS Administrator
INS=Installation Server
SM = System Monitor

Fig. 5 One-NDS 8.0 Functional Components

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . .
CN65301EN86GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
. Nokia
© 2012 . .Siemens
. .Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 One-NDS 8.0 System Architecture

 Provisioning Gateway (PGW)

Provisioning describes the process by which subscribers, services, and other
directory data can be managed in the database based on commands presented by
an external entity, such as a provisioning subsystem. The provisioning gateway
(PGW) provides a flexible, standards-based approach to enable the integration of
operators’ existing provisioning engines and new applications that use the One-NDS
as a common repository. Transactions from the Customer Care Center (CCC)
systems are forwarded to the provisioning gateway, processed there (selecting the
DSA, where the subscriber will be stored), and then forwarded to the Data Base. The
lightweight directory access protocol (LDAP) interface is used to transfer these
transactions over the PGW-DSA to the database. LDAP is based on the X.500
standard, but unlike X.500, LDAP supports TCP/IP access.
 PGW-DSA with integrated functions
1. The Notification Manager (NTF) is a central component for distributing all
notifications from One-NDS components, that is, the NTF is responsible for the
distribution of SOAP trigger messages from the One-NDS Directory to both PGW
and application servers. The NTF stores the subscription information from
different applications in the One-NDS Directory.
2. The Config DSA is used to store the configuration data of the PGW. The
configuration data provides information about the typology of the One-NDS
Directory: number of DSs of routing DSA and PGW DSA, distribution of these
DSAs over geographical sites, number and IDs of BE DSAs, IP addresses,
presence of separate application LAN, presence of PGWs, their IP addresses,
distribution of PGW geographical sites, and so on.
 Subscriber Data Base
The data base where subscribers at stored consists of routing DSA cluster and the
BE-DSA clusters.
The BE-DSA clusters are the part of the directory that does contain the actual data
content.
The routing DSA stores access keys and references to the database entries
(subscriber data).
 System Monitor (SM
The NetAct System Monitor is introduced as an integral part of the One-NDS that
provides standard interfaces that can be integrated to a third party Network
Management System (NMS) for fault and performance management. One-NDS is
integrated to NetAct via the System Monitor. Fault and Performance management
data are collected from One-NDS components by the SM, aggregated and filtered,
then reported to NetAct.
 One-NDS Administrator (ADM)
The One-NDS Administrator (ADM) is an independent management system used for
the administration of One-NDS Directory, PGW configuration, and Notification
Manager (NTF). Over the ADM, authenticated clients and authorized users can
perform tasks, for example, in the One-NDS Directory. The tasks include relocating
subscribers from one BE DSA to another, monitoring subscriber data storage,
schema management, checking data consistency and administrating new DSAs.

CN65301EN86GLA0
14 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

SS7 Application clients

Trigger DB access
SOAP LDAP

SNMP One-NDS 8.0

CORBA Subscriber Data Base
LDAP
@com SSH
HTTP ADM

NTF Config
or
INS
PGW-DSA

NE3S SM
Provisioning Gateway
NAC6

Provisioning
(SPML)

Customer Care Center

Fig. 6 One-NDS Basic Components

TIP
A trigger interface is used to notify application servers (e.g. NT HLR FE, PCS etc.)
about data changes in the One-NDS.

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
15
 One-NDS 8.0 System Architecture

CN65301EN86GLA0
16 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

3 One-NDS - An X.500-Based Directory

One-NDS 8.0 System Architecture

One-NDS – An X.500-Based Directory

Fig. 7

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
17
 One-NDS 8.0 System Architecture

3.1 General
Directories provide a versatile way of organizing information and are highly
appropriate for modeling the typical hierarchical relationships between data objects in
the real world.
For One-NDS, a standard X.500 directory has been selected in accordance with the
International Telecommunication Union’s X.500 series of recommendations as the
preferred structure for arranging information within the directory. Storage capacity is
virtually unlimited and directory performance is not affected by increases in data
volume.

Fig. 8 ITU-T X.500

CN65301EN86GLA0
18 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

The following terms discussed in this course are defined in ITU-T Rec. X.501:
 access control
 alias
 attribute
 attribute type
 attribute value
 Directory Information Tree (DIT)
 Directory System Agent (DSA)
 Directory User Agent (DUA)
 distinguished name (DN)
 entry
 hierarchical group
 object (of interest)
 relative distinguished name (RDN)
 root
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CN65301EN86GLA0
. . . . . . .
© 2012 Nokia Siemens Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 One-NDS 8.0 System Architecture

3.2 The Directory

In simple terms, a Directory is a database that follows the structure and features
defined in the X.500 standards. The data is stored in a directory structure, hence the
term ‘Directory’.
Telecoms applications require fast access to potentially millions of subscriber entries.
The Directory provides this because of two key features:
 Data is held in memory (as opposed to on disk) making access very fast.
 The directory structure allows for efficient retrieval of data
3.2.1 Directory Server (DS)
The primary purpose of the Directory Server (DS) is to provide directory (database)
services to applications, existing within a telecommunications core network.
Tasks of the DS:
At all times, one of the servers in the cluster, termed the primary server (P), is
responsible for handling the update, and then replicating it to all the other servers in
the cluster. If the primary server fails, one of the remaining secondary servers will
assume the primary server’s role. Any of the servers can take on the primary server’s
role.
 handle queries or updates of the database
 replicating the contents of the database between a number of DS nodes
 forwarding alarms to a remote system

3.2.2 Directory System Agent (DSA)

The directory system agent (DSA) is a collection of DS platforms, which operate in a
redundant manner to provide data to interrogating systems. The data within each DS
contained in a DSA is identical. Only one DS within a DSA can receive updates
regarding the data. This DS known as the primary DS is then responsible for
replicating the data to all the secondary DSs. The secondary DSs can only take part
in database queries. This is because within a cluster, only one system can be the
authority to maintain consistency within the cluster.

CN65301EN86GLA0
20 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

R-DSA DS DS DS DS DS

DS DS P

sync sync sync sync

DSA DSA
BE-DSA
DS DS DS DS
sync sync
P

Fig. 9 DS and DSA

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . .
CN65301EN86GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
. Nokia
© 2012 . .Siemens
. .Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 One-NDS 8.0 System Architecture

3.3 Distribution of data

The database has two logical components: the routing DSA and the BE-DSA.
 The routing DSA (R-DSA) stores access keys and references to the database
entries (subscriber data). It holds only the information that is necessary to route
LDAP requests to the BE-DSA. The number of DSs in the routing DSA depends on
the total data stored in the BE and on access frequency. To ensure persistence
and redundancy, at least three DSs should be used. Each routing DS contains the
same data. This means that there is only one routing DSA with the appropriate
number of DSs.
 The BE-DSAs store subscriber data. To ensure persistence, each BE-DSA
consists of three servers. One BE-DSA holds data for a maximum of 4 million
subscribers (depends on the size of a subscriber profile), which means that there
are "n" number of BE-DSAs in a network, where each BE-DS can be in another
geographical location.
 A One-NDS 8.0 system supports up to 60 DSA's. The maximum number of DS's
per DSA and the associated limit on the size of a DSA remains the same.

CN65301EN86GLA0
22 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

HLR HSS EIR

applications

R-DSA

key, location DS DS DS DS DS
and configuration
information

DS DS
BE-DSA
subscriber data sync sync sync sync
DSA DSA
DS DS DS DS
sync sync

Fig. 10 Data Distribution Between Back End DSA and Routing DSA

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CN65301EN86GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
© 2012
23
. Nokia
. .Siemens
. .Networks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 One-NDS 8.0 System Architecture

3.4 Directory Service

The distributed One-NDS Directory is made up of directory system agents. In a DSA,
one DS is the primary server and the other DSs are secondary servers. All DSs of a
DSA store the same data. Modifications of this data (for example, adding a new
subscriber object or changing the location information of a subscriber) are performed
on the primary server.
The data of the secondary servers is synchronized by a replication mechanism. Read
operations to the directory can be performed by the primary and the secondary
servers. The data is only written to the local disk for backup operations.

Primary: is responsible for controlling the application and replication of updates to

the database.
Secondary Synchronized: is up-to-date with updates replicated from the Primary
mode server.
Secondary Unsynchronized: is not receiving updates from the Primary mode server
e.g.: due to a network fault.

The Primary mode server will nominate one of the Secondary Synchronized mode
servers to run as the Primary Standby. The Primary Standby server carries the
responsibility of taking over the Primary role if it detects a Primary server failure.

CN65301EN86GLA0
24 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

• primary (P)

• secondary synchronized (SS) • secondary synchronized (SS)

• primary standby (PS)

Fig. 11 Synchronized Status

• primary (P)

• secondary unsynchronized (SU) • secondary synchronized (SS)

• primary standby (PS)

Fig. 12 Unsynchronized Single DS

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
25
 One-NDS 8.0 System Architecture

3.5 In-memory database

To meet the demanding performance requirements implicit in providing
telecommunications services, One-NDS maintains all data in memory storage for the
fastest possible access.
For availability reasons (since memory is a volatile storage medium) each DSA is
actually realized by a number of synchronized physical servers (servers). Each
server within a DSA has an identical copy of the data which represents the portion of
the directory held by that DSA.

read data from the memory

(queries)

DSA

Fig. 13 Read Data from the Memory (BE-DSA)

CN65301EN86GLA0
26 © 2012 Nokia Siemens Networks
One-NDS 8.0 System Architecture

update e.g.
• modify subscriber
• Location update

replication

PS/SS DSA SS

Fig. 14 Update Operation

CN65301EN86GLA0
© 2012 Nokia Siemens Networks
27
 One-NDS 8.0 System Architecture

3.6 Summary
 Directory is a database that follows the structure and features defined in the X.500
standards.
 The X.500 standard defines a protocol (among others) for a client application to
access the X.500 directory, called the Directory Access Protocol (DAP).
 External clients are accessing the data base via LDAP
 The data are stored on directory servers (DS)
 Several DS build a directory system agent (DSA)
 One DS in an DSA is always primary
 All other DS in a DSA are secondary synchronized.
 Updates can only handled by the primary
 Queries can be handled by every DS.
 All data are held in the memory

CN65301EN86GLA0
28 © 2012 Nokia Siemens Networks