01 OHC508102 USCDB System Introduction (VHSS) ISSUE1.00

USCDB Software
System Overview
www.huawei.com
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

References
l  HSS9860V500R009 Product Manual-software description
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved. Page2
Objectives
l  Upon completion of this course, you will be able to:
p  Understand software system structure of SingleSDB;
p  Understand the required software for installation;
p  Master the structure, interface, function of each subsystem
p  Understand the USCDB software reliability
Contents
1.  USCDB Software Structure Overview
2.  USCDB Subsystem Introduction
3.  USCDB software
4.  USCDB License
5.  USCDB Reliability Design
Contents
1.1 Virtualization Software Structure Introduction
1.2 SingleSDB Overall structure and USCDB software structure
1.3 USCDB Concept introduction and function list
FusionSphere software architecture
Platform application software
OMU software architecture
LMT software architecture
vCMM software architecture
l  vCMM: The vCMM locates at the NE/network management layer in the NFV
standard. It is positioned as the Virtual Network Function Manager(VNFM) and can
manage the life cycle of virtual NEs. Working in browser/server (B/S) mode. The
user only needs to update the software on the server during system upgrade or
maintenance. This helps reduce the load on the computer running the browser and
simplify system upgrade and maintenance.
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

l  Page10
NE Software Strcture
Contents
1.2 SingleSDB Overall structure and USCDB software

structure
Overall structure
USCDB software structure
GU FE plug HSS FEplug PGW

iManager
MCI DCI LDAP SQLAPI SOAP
UDB(In Memory database)/oracle database

CGP Platform
Linux
CGA Hardware Platform
l  USCDB software structure is a distributed system, each

functional module is located in OSTA 2.0.
Contents
1.2 SingleSDB Overall structure and USCDB software structure
Concept introduction
l  DRU and DSU Nodes
p  A node refers to a unit that can independently provide services.
The node can be classified into two types:
n  Master node: A node that can provide data services such as
adding, deleting, modifying, and querying data.
n  Slave node: A node that can provide only data querying service.
p  DRU/DSU nodes and DRU/DSU modules are in one-to-one

relationship.
l  Cluster
p  A cluster refers to a group of nodes that manage the same
data, consists of one master node and several slave nodes.
Concept introduction (Cont.)
l  DRU Cluster
l  DSU Cluster
Node State Description

INACTIVE The node in this state does not provide services.
ABNORMAL It indicates that the node is faulty.
INITIAL The node is in this transition state when it is being
started.
LOADING It indicates that the node is being loaded with data.
LOADED It indicates that the node loading is completed.
STARTED It indicates that the node initialization is completed.
SLAVE The node is a slave node, which can provide only data
querying service.
PRE-MASTER The node is a pre-master node. The node is in this
transition state during node election.
MASTER The node is the master node, which can provide data
querying and data updating services.
l  Node Election
p  Node re-election affects service processing. If no master node
is available in a cluster, update operations fail. If multiple
master nodes are available in a cluster, update operations
result in data inconsistency.
l  Heartbeat Management
p  Based on the information contained in the heartbeat messages
n  a node election is initiated in the DS clusters.
n  a node is selected to process service messages.
n  notifies other locations of the local cluster states .
l  Data Replication
p  To ensure data consistency between the master node and slave

nodes in the same DRU or DSU cluster and between the active and
redundancy USCDBs, the master node must replicate updated data to
other nodes. .
p  Data replication is classified into:
n  Synchronous replication and asynchronous replication.
n  Inter-location replication and intra-location replication.

l  Data Synchronization
p  Data synchronization is the process in which the data updated in the

in-memory database of the DRU or DSU is synchronized to the
physical database to ensure data consistency.
Data Replication
l  Static data refers to the data specific to subscribers and is valid in

the long term and irrelevant to the activity status of subscribers,
for example, IMSI, MSISDN, and subscribed service information.
l  Dynamic data refers to the data generated or recorded during

movement of subscribers and is valid for a given period of time,
for example, subscriber location and status.
Data Synchronization
l  According to the data type, data synchronization includes the

following:
p  Synchronization of static data, including global data, routing data,
subscriber ID, subscription data, and authentication data
p  Synchronization of dynamic data, including location information and

subscriber status
Function list
l  Functionally, USCDB can be classified into:
p  DRU: Data Routing Unit
p  DSU: Data Service Unit
p  PGW: Provisioning Gateway
p  DSG: Data Service Gateway
p  DBG: Database Gateway
p  DPU: Dispatch Packet Unit
p  NDF: Network Data Function
p  DTL: Data Tool
p  DBMS: Database Management System
p  OMU: Operation and Maintenance Unit
Contents
4.  USCDB License
Contents
2.1 Subscriber Data Management Subsystem
2.2 Service Processing Subsystem (for the UPCC)
2.3 Data Service Subsystem
2.4 Data Storage Subsystem
2.5 O&M Subsystem
Subscriber Data Management
Subsystem
l  PGW: provisioning gateway
l  DTL: data tool
l  DPU: dispatching unit

Subsystem (Cont.)
l  Interfaces provided by the subscriber data management
subsystem
Subsystem (Cont.)
l  Message distribution policies of subscriber data management
including:
p  DPU distribution policy
p  PGW distribution policy
Contents
2.5 O&M Subsystem
Service Processing Subsystem (for the
UPCC)
l  Functional structure of the subscriber data management
subsystem
Service Processing Subsystem (for
the UPCC)(cont.)
l  Interfaces provided by the subscriber data management
subsystem
Service Processing Subsystem (for
the UPCC)(cont.)
l  Message distribution policies of subscriber data
management including:
p  NPU distribution policy
p  PPU distribution policy
p  SPU distribution policy
p  SDU distribution policy
p  DSG distribution policy
Contents
2.5 O&M Subsystem
Data Service Subsystem
l  Functional structure of the data service subsystem
p  The in-memory database implements the subscriber data
query and modification during service processing. It adopts the
UDB software and is deployed in board memory.
Data Service Subsystem (Cont.)
l  Interfaces provided by the data service subsystem
Data Service Subsystem (Cont.)
l  Message distribution policies of data service subsystem
including:
p  DSG distribution policy
p  DRU distribution policy
p  DSU distribution policy
Contents
2.5 O&M Subsystem
Data Storage Subsystem
l  Functional structure of the data storage subsystem
p  The physical database is a device for storing data permanently.
It is independent of service processing.
Data Storage Subsystem (Cont.)
l  Interfaces provided by the data storage subsystem
l  Message Distribution Policies
p  The DBG modules work in load-sharing mode.
p  The DRU and DSU modules send messages to the DBG

modules on a random basis.
l  Data Storage Mechanism
p  Global data
p  Subscriber data
p  Routing data
p  PGW operation logs
l  Data Storage Mechanism
p  Data stored in the physical database
n  Global data
n  Subscriber data
n  Routing data
n  PGW operation logs
p  TableSpace Planning
Storage Information User Name Password Rights Default Tablespace

Subscriber data, routing data, and uscdb huawei DBA usrts
global data
PGW operation logs pgw huawei DBA pgwts
Contents
2.5 O&M Subsystem
O&M Subsystem
l  Position of the OMU on the network
O&M Subsystem (Cont.)
l  OMU mainly provides the following functions:
p  Transfers the MML commands from LMT to DSU/DRU
modules;
p  Transfers the response from DSU/DRU modules to

corresponding LMT;
p  Stores and transfers alarm information and performance

measurement information;
p  Provides a interface connected to network management

system, to implement centralized management;
Questions
l  Based on the messages from PGW web client or BOSS
system, how does DPU choose PGW modules?
l  What is the relationship between PGW1 and load PGW?
l  Under what kind of scenario, system will use the SQLAPI

interface?
Contents
4.  USCDB License
Software on the OMU process
l  The OMU process implement the functions of the O&M
subsystem. They are installed with the following software:
p  Operating system: Novell SUSE Linux Enterprise Server 10
SP3 for x86_64
p  Database software: OMU database
p  Version software: OMU application software
Software on the USCDB process
l  USPGW process
p  implement the functions of the subscriber data management
subsystem. They are installed with the following software:
n  Operating system: Novell SUSE Linux Enterprise Server 10 SP3 for
x86_64
n  Version software: USCDB application software
l  USRSU, USDRU and USDSU process

p  implement the functions of the data service subsystem. They are
installed with the following software:
n  Operating system: Novell SUSE Linux Enterprise Server 10 SP3 for
x86_64
Software on the USCDB process (Cont.)
l  USPMU and USDMU process
p  The USDMU process implement the functions of the data
storage subsystem, the USPMU process implement the
functions of the subscriber data management subsystem and
data storage subsystem.
p  They are installed with the following software:
n  Operating system: Novell SUSE Linux Enterprise Server 10 SP3
for x86_64
n  Database software: Oracle Database 11g Enterprise Edition
Release 11.1.0.7.0 (Server/Client)
Contents
4.  USCDB License
License Control of USCDB
l  The license control center and license agent implement
license control.
Module Function
License control center The license control center implements the
following functions:
• Loads the license file from the OMU and
analyzes the license file.
• Controls the license configuration.
• Processes maintenance commands.
• Verifies and synchronizes the license file among
all the license agents in an NE.
License agent The license agent provides an API interface for
the modules of an NE to query the license
configuration.
License Control of USCDB (Cont.)
l  Control Mechanisms for Resource Control Items
p  The number of subscribers is counted as follows:
n  The number of static subscribers is counted according to the data
in the in-memory database every early morning.
n  The number of dynamic subscribers is counted according to the

data in the DSU every early morning.
n  The PGW updates the number of other types of subscribers in the

DRU every 20 seconds.
License Control of USCDB (Cont.)
l  Control Mechanisms for Resource Control Items
p  The number of subscribers is controlled as follows:
n  90% ≤ Number of subscribers < 100%
–  All the operations are allowed. A fault alarm with the severity level of
Warning is generated. This alarm is cleared when the number of
subscribers falls below 89% of the limit specified in the license file.
n  100% ≤ Number of subscribers <102%

–  All the operations are allowed. A fault alarm with the severity level of
Critical is generated. This alarm is cleared when the number of
subscribers falls below 99% of the limit specified in the license file.
n  102% ≤ Number of subscribers

–  Subscriber definition and service provisioning are restricted.
Contents
4.  USCDB License
Contents
5.1 Flow Control
5.2 Data backup and Verification
Flow Control (Cont.)
l  Flow Control of the Signaling Processing Subsystem
p  GU-HLR Flow Control of the Signaling Processing Subsystem
p  IMS-HSS Flow Control of the Signaling Processing Subsystem
p  SAE-HSS Flow Control of the Signaling Processing Subsystem
p  UEIR Flow Control of the Signaling Processing Subsystem
p  ENS Flow Control of the Signaling Processing Subsystem
l  Flow Control of the Data Service Subsystem
p  Flow control requires the data service subsystem to process
maximum number of messages within its processing capability
and discard the messages that exceed the processing
capability in the case of surging traffic.
p  The data service subsystem adjusts the traffic volume of each

node according to the CPU usage and the message queue
delay.
l  Flow Control of the Subscriber Management Subsystem
p  Flow control allows the PGW to limit the number of commands sent
from the provisioning system within the specified range, thus
preventing congestion or overload from the links between the PGW
and the provisioning system and ensuring normal processing of
commands.
n  On receiving commands from the provisioning system, the PGW evaluates
the current processing capability based on the average delay of command
processing and the CPU usage of process.
–  If the number of commands to be processed within the specified period exceeds
the maximum processing capability of the PGW, the PGW suspends the batch
operation that is being performed and discards certain commands to protect the
system against overload.
Contents
5.1 Flow Control
5.2 Data backup and Verification
Data Backup
l  Data Backup contains 3 types backup:
p  OMU System Backup
p  Data Backup of the In-Memory Database
p  Data Backup of the Physical Database
OMU System Backup
l  Automatic backup
p  Can be classified into automatic local disk backup and network
disk backup.
n  Automatic l local disk backup: is performed automatically once a
day at 03:30. The OMU retains the database backed up during the
last seven days.
n  automatic network backup: backup time can be performed as

required. SET BKPPOLICY
l  Manual backup
p  can be divided in to local disk backup and network disk backup.
BKP SYS
Data Backup of the In-Memory Database
l  Backing Up Data to Slave Nodes
n  Master node automatically
copies the updated data to the
slave nodes in the same cluster.
l  Backing Up Data to virtual

machines
Two methods are available for
backing up IMDB data to the virtual
machines.
–  Automatic backup
–  Manual backup: BKP NODE
l  Backing Up Data to the Physical

Database
Data Backup of the Physical
Database
l  Backup of Physical Database
p  During physical database backup, all subscriber data and control file
of the Oracle database are backed up, it is full backup.
p  According to the place to be backed up, the backup of the physical

database includes Network Backup.
n  Network Backup: “MML Command – USCDB” MOD BACKUP
p  According to the backup methods to be used, physical database

backup is classified into automatic backup and manual backup.
n  Automatic backup: perform an automatic backup at 04:00:00 every day.
n  Manual backup: “MML Command – USCDB” BKP DB
Data Verification
Method Trigger Point Remarks
Exception During data replication, if the master • If the check is successful, the master
check node fails to receive a response node deletes the exception check
from the slave node within the logs.
specified time or fails the replication, • If the check times out or fails, the
the master node records the master node retains the exception
exception check logs. Then, the check logs and starts another check.
master node initiates an exception • If the data check times out and fails
check. for three times consecutively, the
master node generates a check failure
alarm. The master node retains the
exception check logs until the check is
successful.
Periodic data Data consistency between the • Horizontal forward or backward check
check master node and slave nodes in a is within a cluster, and is performed
cluster against the data stored in the master
Data consistency between the DSU node.
and DRU nodes • Vertical forward or backward check is
Periodic data check between the performed against the data stored in
active and redundancy USCDBs is the DSU node.
performed to ensure data
Copyright © 2017consistency between
Huawei Technologies theAllUSCDBs.
Co., Ltd. rights reserved. Page64
Data Verification (Cont.)
Method Trigger Point Remarks
Single After receiving a single The data check for a single subscriber
subscriber subscriber check message involves vertical check and horizontal
check from an FE, the DRU node and check. The vertical check is performed
the DSU node check the before the horizontal check.
routing data and subscriber
data of the subscriber stored in
slave nodes against the data
stored in master nodes.
Check of the By default, the system checks The check is performed against the data in
in-memory and the data in the in-memory the in-memory database. During each
physical database and the physical check, the system obtains the data records
databases database every two hours. You from the primary key table of the in-
can change the check period memory database one by one, and then
by modifying a software obtains the relevant records from the
parameter. corresponding auxiliary key table. Then,
the system compares the records with
those stored in the tables of the physical
database.
Questions
l  How to define the auto-backup time of physical database?
l  For single subscriber check, what verification principle
should be followed?
Summary
l  This course mainly discuss about the component of USCDB
and structure, interfaces, functions, messages distribution
policy of each component; at the same time, the license
control principle and reliability design are also included.
Thank you!
www.huawei.com

01 OHC508102 USCDB System Introduction (VHSS) ISSUE1.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 OHC508102 USCDB System Introduction (VHSS) ISSUE1.00

Uploaded by

Copyright:

Available Formats

USCDB Software

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

p Understand the required software for installation;

p Master the structure, interface, function of each subsystem

p Understand the USCDB software reliability

3. USCDB software

4. USCDB License

5. USCDB Reliability Design

1.2 SingleSDB Overall structure and USCDB software structure

1.3 USCDB Concept introduction and function list

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

1.2 SingleSDB Overall structure and USCDB software

1.3 USCDB Concept introduction and function list

GU FE plug HSS FEplug PGW

UDB(In Memory database)/oracle database

l USCDB software structure is a distributed system, each

1.2 SingleSDB Overall structure and USCDB software structure

1.3 USCDB Concept introduction and function list

p DRU/DSU nodes and DRU/DSU modules are in one-to-one

Node State Description

p To ensure data consistency between the master node and slave

p Data replication is classified into:

n Synchronous replication and asynchronous replication.

n Inter-location replication and intra-location replication.

p Data synchronization is the process in which the data updated in the

l Static data refers to the data specific to subscribers and is valid in

l Dynamic data refers to the data generated or recorded during

l According to the data type, data synchronization includes the

p Synchronization of dynamic data, including location information and

3. USCDB software

4. USCDB License

5. USCDB Reliability Design

2.2 Service Processing Subsystem (for the UPCC)

2.3 Data Service Subsystem

2.4 Data Storage Subsystem

2.5 O&M Subsystem

l PGW: provisioning gateway

l DTL: data tool

l DPU: dispatching unit

p PGW distribution policy

2.2 Service Processing Subsystem (for the UPCC)

2.3 Data Service Subsystem

2.4 Data Storage Subsystem

2.5 O&M Subsystem

p PPU distribution policy

p SPU distribution policy

p SDU distribution policy

p DSG distribution policy

p DPU distribution policy

2.2 Service Processing Subsystem (for the UPCC)

2.3 Data Service Subsystem

2.4 Data Storage Subsystem

2.5 O&M Subsystem

p DSG distribution policy

p DRU distribution policy

p DSU distribution policy

2.2 Service Processing Subsystem (for the UPCC)

2.3 Data Service Subsystem

2.4 Data Storage Subsystem

2.5 O&M Subsystem

p The DRU and DSU modules send messages to the DBG

l Data Storage Mechanism

p PGW operation logs

p  Understand the required software for installation;

p  Master the structure, interface, function of each subsystem

p  Understand the USCDB software reliability

3.  USCDB software

4.  USCDB License

5.  USCDB Reliability Design

l  USCDB software structure is a distributed system, each

p  DRU/DSU nodes and DRU/DSU modules are in one-to-one

p  To ensure data consistency between the master node and slave

p  Data replication is classified into:

n  Synchronous replication and asynchronous replication.

n  Inter-location replication and intra-location replication.

p  Data synchronization is the process in which the data updated in the

l  Static data refers to the data specific to subscribers and is valid in

l  Dynamic data refers to the data generated or recorded during

l  According to the data type, data synchronization includes the

p  Synchronization of dynamic data, including location information and

3.  USCDB software

4.  USCDB License

5.  USCDB Reliability Design

l  PGW: provisioning gateway

l  DTL: data tool

l  DPU: dispatching unit

p  PGW distribution policy

p  PPU distribution policy

p  SPU distribution policy

p  SDU distribution policy

p  DSG distribution policy

p  DPU distribution policy

p  DSG distribution policy

p  DRU distribution policy

p  DSU distribution policy

p  The DRU and DSU modules send messages to the DBG

l  Data Storage Mechanism

p  PGW operation logs

n  PGW operation logs

p  Transfers the response from DSU/DRU modules to

p  Stores and transfers alarm information and performance

p  Provides a interface connected to network management

l  What is the relationship between PGW1 and load PGW?

l  Under what kind of scenario, system will use the SQLAPI

3.  USCDB software

4.  USCDB License

5.  USCDB Reliability Design

p  Database software: OMU database

p  Version software: OMU application software

l  USRSU, USDRU and USDSU process

3.  USCDB software

4.  USCDB License

5.  USCDB Reliability Design

n  The number of dynamic subscribers is counted according to the

n  The PGW updates the number of other types of subscribers in the

n  100% ≤ Number of subscribers <102%

n  102% ≤ Number of subscribers

3.  USCDB software

4.  USCDB License

5.  USCDB Reliability Design

p  GU-HLR Flow Control of the Signaling Processing Subsystem

p  IMS-HSS Flow Control of the Signaling Processing Subsystem

p  SAE-HSS Flow Control of the Signaling Processing Subsystem

p  UEIR Flow Control of the Signaling Processing Subsystem

p  ENS Flow Control of the Signaling Processing Subsystem

p  The data service subsystem adjusts the traffic volume of each

p  Data Backup of the In-Memory Database

p  Data Backup of the Physical Database

n  automatic network backup: backup time can be performed as

l  Backing Up Data to virtual

–  Manual backup: BKP NODE

l  Backing Up Data to the Physical

p  According to the place to be backed up, the backup of the physical

p  According to the backup methods to be used, physical database