Huawei CBS A A GDR Solution PDF

Security Level:
Huawei CBS V500R005C30

Active-Active Disaster Recovery Solution
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.

Contents
 A-A DR Architecture
 Deployment
 Data Replication
 Solution and RTO for different scenarios in case disaster strikes
 Data loss
 Impact on Performance and Dimensioning
Active-Active DR Architecture – High Level Active app
App
Site A (Main Site) BMP BMP Site B
App Standby app
BMPD BMPD Single-node

B B
USRDB USRDB Two-node
GMDB GMDB GMDB GMDB Peer to peer

CDRDB CDRDB cluster
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4 Production
business flow
BillDB BillDB
DR business flow
Data replication
CBPAdapte
CBPAdapter CBPAdapte
CBPAdapter
1r 2r
GMDB GMDB
SEE SEE SEE SEE

DCC
FEP/ FEP/
USAU FEP FEP USAU
USAU2
USAU1 GFEP GFEP
EMPP
SMPP+
CAP/MAP/INAP If SMSC/MMSC sends DCC messages,
Core Network GGSN/ then SMSC/MMSC talks to CBPAdapter
MSC/STP SMSC MMSC directly.
PGW
HUAWEI TECHNOLOGIES CO., LTD. Huawei proprietary. No spread without permission. Page 4
Active-Active DR Architecture – Low Level
See next page for Architecture in Low Level
Notes:
1. CRM/ESB is assumed to send requests to BMP Cluster 1 in site A via BMPGateway1.
2. BMP Custer 1 is Active while BMP Cluster 2 is Standby.
3. CBP & CBPAdapter are in Active-Active model, each site with 100% capacity, 50% production traffic.
4. OCG(SEE) is in all active mode.
Scenarios:
1. Operation & Management
a. BMP of Site A writes the updates to physical database (BMPDB, SYSDB, USRDB etc) and when the transaction is committed
the updates will be synchronized/written in Site B due to the mechanism of physical database.
b. At the same time, the updates will be synchronized to both GMDB of Site A & Site B from the physical database of Site A.
2. Calling & Data Usage & Other Service

a. When the CBP updates the GMDB and these updates don’t need to be written to physical database, these updates will be
synchronized from GMDB of site A to GMDB of site B or vice versa, depending on which site receive and process the traffic.
b. When the CBP updates the GMDB and these updates need to be written to physical database. No matter which site
processes the traffic, the updates will first synchronized to physical database of site A and then written to site B.
Acronyms
BMP: Business Management Point
In the Huawei OCS solution, the BMP implements service operation management, and provide system management, product
management, Offer Management, resource management, customer management & customer service Management. External
CRM/CC system which provides the GUI for subscribers and telecom operators can invoke these functions.
CBP: Convergent Billing Point

In the Huawei OCS solution, the CBP implements rating, charging and accounting functions and supports online charging.
For online charging, after receiving the charging & authentication request from the OCG, the CBP performs budget and account
reservation for the conversation duration, and indicates the conversation duration to the OCG. After receiving the charge
deduction request from the OCG, the CBP deducts the expense in real time.
GMDB: General Memory Database

A Huawei-developed relational database system designed based on physical memory and database industry standards. The GMDB
is applied to the applications that require high-performance database access and real-time processing.
OCG: Online Control and Charging Gateway

OCG provides online call and charging control and routing service.
SEE: Service Execution Environment

FEP/GFEP: General Front End Processor
USAU: Universal Signaling Access Unit
BMPGatew
BMPGatew BMPGatew
ay
ay
Site A (Main Site) ay Site B
App Active app
BMP1 BMP3
w, r App Standby app
w, r BMPD BMPD Single-node
B B
Invoicin
USRDB USRDB Two-node
Invoicin Invoicin
gg g
GMDB GMDB Peer to peer
CDRDB GMDB GMDB CDRDB cluster
BillMgm CBP1 BillMgm
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4 Production
t t
business flow
BillDB BillDB
DR business flow
Data replication
Report Report
CBPAdapte
CBPAdapter
w: write
r 1r 2r r
Mediatio GMDB GMDB Mediatio r: read
n n
I2000
I2000 SEE SEE SEE SEE
DCC
FEP/ FEP/
USAU FEP FEP USAU
USAU2
USAU1 GFEP GFEP
EMPP
SMPP+
CAP/MAP/INAP
If SMSC/MMSC sends DCC messages,
Core Network then SMSC/MMSC talks to CBPAdapter
MSC/STP GGSN SMSC MMSC directly.
DR Deployment Scheme -1/2
NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma Remark
nual
CBPAdapter A-A Two-node cluster (100% capacity, Two-node cluster (100% capacity, Both GMDB in site 1/2 is divided to two schemes and
(incl. GMDB) 50% production traffic) 50% production traffic) each scheme adopts one-way data replication.
CBP (incl. A-A Two-node cluster (100% capacity, Two-node cluster (100% capacity, Both GMDB in site 1/2 is divided to two schemes and
GMDB) 50% production traffic) 50% production traffic) each scheme adopts one-way data replication.
USAU A-A Two-node cluster (100% capacity, Two-node cluster (100% capacity, Both No date replication
50% production traffic) 50% production traffic)
FEP/GFEP A-A Two-node cluster (100% capacity, Two-node cluster (100% capacity, Both No data replication
50% production traffic) 50% production traffic) 1，Depends on whether SMSC/MMSC support
polling mode.
SEE (i.e. OCG) A-A N+1 cluster (load balancing, N+1 cluster (load balancing, Both In case N=1, Site 1/2 will be deployed with 1+1 boards；
100% capacity, 50% production 100% capacity, 50% production In case N>=2, Site 1/2 will be deployed with N boards. (N is
traffic) traffic) enough because N provides 100% capacity while 50%
traffic is handled)
BMPGateway A-S Two-node cluster (100% capacity, Single-node system (100% Both No date replication
(SLB) 100% production traffic) capacity, 0% production traffic)
BMP A-S N+1 cluster (100% capacity, N+1 cluster (100% capacity, 0% Both Including UPC/GL/AR/DC/CDRQuery
100% production traffic) production traffic)
BMPDB(SYSD A-S Two-node cluster (100% capacity, Single-node system (100% Both Oracle Active Data Guard is used for data replication.
B) 100% production read traffic, capacity, 0% production read
100% production write traffic) traffic, 0% production write traffic)
DR Deployment Scheme- 2/2 (End)
NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma Remark
nual
USRDB A-S Two-node cluster (100% capacity, Single-node system (100% Both
100% production read traffic, capacity, 0% production traffic)
100% production write traffic)
CDRDB, BillDB A-S Two-node cluster (100% capacity, Single-node (100% capacity, 0% Both .
SDU Currently SDU is deployed along with USRDB in the same board, the mode and deployment is same as USRDB;
In future, SDU will be replaced by memory DB (OMDB), the mode and deployment is same as SEE.
Invoicing A-S Two-node cluster (100% capacity, Single-node (100% capacity, 0% Both
Bill A-S Single-node (100% capacity, Single-node (100% capacity, 0% Both
Management 100% production traffic) production traffic)
Report A-S Single-node (100% capacity, Single-node (100% capacity, 0% Both By default, DR is not supported/suggested.
100% production traffic) production traffic) In case of DR, only reports will be replicated, the
source file will not be replicated to the DR site.
Mediation A-S Single-node (100% capacity, 50% Single-node (100% capacity, Both No date/file replication
production traffic) 50% production traffic)
I2000 A- Two-node cluster or single- Single-node (100% capacity, 0% Both If I2000 is deployed in Main site in dual-node cluster,
S(Optio node(100% capacity, 100% production traffic) then DR is not supported;
nal) production traffic) If I2000 is deployed in Main site in single node, then
DR can be supported, we can deploy a I2000 in
single-node in DR site.
Oracle GoldenGate Data Replication
Site A (Main Site) Site B

OGG operations
Oracle operations
Source Target
Oracle DB Oracle DB
Online
1. The Oracle GoldenGate (OGG) of the
redo logs source DB extracts data from the redo log
and archive log and writes the data into a
3, Apply local trail file.
Archived 1, Extract 2. OGG sends the trail file generated by the
redo log source DB to target DB.
files 2.1 Send 2.2 Receive 3. The OGG of the target DB reads the trail
Trail files Network Trail files file content and applies the file content to
the target DB to synchronize data.
Date Replication for BMPDB and USRDB App Active app
App Standby app
Site A (Main Site) BMP BMP Site B Single-node

1 3
read
Cach Cach Two-node
e e
write Peer to peer
cluster
BMPD BMPD Production
Write, read B B business flow
(Read-write (Read-only DR business flow
status) status) Data replication
USRDB USRDB
w: write
write write write r: read
(Read-write write (Read-only
status) Cache Cache status)
Cache Cache
r GMDB r GMDB
r r
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
r r
SEE SEE SEE SEE
Cache Cache Cache Cache
 For BMPDB/USRDB , Huawei use Oracle DB, the Replication solution will use Oracle Golden Gate. License fee needs to be considered.
 BMPGateway + BMP+BMPDB are deployed in one DR switch group.
Date Replication for USRDB – Low Level : Asynchronous
Replication
Site A Site B
Active Active
Application Application
1. Update
1. Update
2. Send change
USRDB USRDB
replication engine
3. Update (remote change)

 To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication
 The related application includes BMPAPP, CBPAPP.
Date Replication for GMDB – High Level
GMDB GMDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
CBPAdapte
CBPAdapter
1r 2r
GMDB GMDB
For Memory DB, it is made by Huawei, it support high performance service processing. Consider to the
performance, the data replication also adopt Asynchronous Replication solution.
Date Replication for GMDB – Low Level : Asynchronous
Replication
Site A Site B
Active Active
Application Application
1. Update 1. Update
2. Send change
GMDB GMDB
Scheme Scheme
1a replication engine 1b
Scheme Scheme
2b 2a
 To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication
 The related application includes CBPAPP, CBPAdapter
Routing
 There is routing table in CBPAdapter(GMDB), so it can know which CBP to route.
 All the routing table in each site are same and keep the FULL routing data. So when one CBP is down,
CBPAdapter can route the request to the other CBP.
 CBPAdapter first checks the routing table of discrete number, if the MSISDN is not found in it, segment
based routing will be applied.
GMDB GMDB GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
135* 138* 135* 138*
CBPAdapte
CBPAdapter
1r 2r
GMDB GMDB
Virtual GT of OCG(SEE)
 SEE cluster in both sites share the same Virtual GT (GT3). SEE cluster in site A has a real GT(GT1), SEE cluster in site B has
a real GT(GT2)。
 STP is assumed to support polling.
 USAU1 in Site A talks to SEE cluster in Site A only, while USAU2 in Site B talks to SEE cluster in Site B only.
MSC STP USAU1 SEE SEE USAU2 SEE SEE
IDP(DGT=GT3)
IDP(DGT=GT3)
IDP(DGT=GT3)
RRBE(OGT=GT1)
RRBE(OGT=GT1)
RRBE(OGT=GT1)
ERB(DGT=GT1)
ERB(DGT=GT1) ERB(DGT=GT1)
IDP(DGT=GT3)
IDP(DGT=GT3)
IDP(DGT=GT3)
RRBE(OGT=GT2)
RRBE(OGT=GT2)
RRBE(OGT=GT2)
Scenario1: When CBP (APP2) is down
BMP BMP Connection stopped
Site A (Main Site) 1 3 Site B Connection applied
w, r w r
w, r BMPD BMPD r Production
B B business flow
USRDB USRDB DR business flow
Data replication
GMDB GMDB
CDRDB GMDB GMDB CDRDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
1. DR software monitors links
1r 2r
GMDB GMDB between CBPAgent and
CBP.
2. When DR software detects
SEE SEE SEE SEE that CBP2 is down, DR
software notifies CBPAgent
to change the routing, that
is, talks to CBP4 in Site B
instead of CBP2 in Site A.
The change can be done
automatically or manually
Scenario1: CBP GDR switchover flow
GDR switchover duration: 3s

RTO/Downtime：
3s System
switch
Single node Dual cluster
failure switch Service
failure takeover
Time
Dual cluster Disaster System switch schedule
switch detection（About less than 3s）
In case of Manual The GDR software:

Switch: Depending 1. Check the CBP data replication link, if it is not
on decision stopped, stop it.
mechanism; 2. Set the CBP2 status to faulty in system
In case of
Automatic Switch:
definition table in BMPDB(SYSDB), update the
Configurable, status of CBP2 into the cache of other normal
about 10minutes CBPs and CBPAdapter. Then CBPAdapter
automatically change routing.
Scenario2: When CBP Adapter1 is down
Site A (Main Site) Site B Connection stopped
Connection applied
Production
business flow
DR business flow
GMDB GMDB Data replication
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
CBPAdapte
CBPAdapter
1r 2r
GMDB GMDB
SEE SEE SEE SEE

DCC
FEP/ FEP/
FEP FEP
GFEP GFEP
EMPP
SMPP+
Core Network
MSC/STP GGSN SMSC MMSC
Scenario 2: CBP Adapter Rerouting Flow
GDR switchover duration: 10s
RTO/Downtime：
10s System
switch
Single Dual cluster
node switch Service
failure failure takeover
Time
Dual cluster Disaster Rerouting (About schedule
switch detection less than 10s）
In case of Manual The GDR software:

Switch: Depending 1. Check the CBPAdapter data replication link, if it is
on decision not stopped, stop it.
mechanism; 2. Set the CBPAdapter1 status to faulty in system
In case of Automatic definition table in BMPDB(SYSDB), update the
Switch: status of CBPAdapter1 into the cache of every CBP
Configurable, about and SEE. Then SEE automatically change routing.
10minutes SEE automatically set the CBPAdapter1 status to
faulty and will not send requests to CBPAdapter1.
Scenario 3.1.1: When OCG(SEE) is down (i.e. number of faulty SEE<=2), no need
to switch
Site A (Main Site) Connection stopped
BMP BMP Site B
1 3 Connection applied
CBPAdapte
CBPAdapte CBPAdapte
CBPAdapte
rr rr
GMDB GMDB
Automatic switchover
decision mechanism:
SEE SEE SEE SEE SEE SEE SEE SEE SEE SEE 1. In case the number
of SEE where
exception happens
reaches X, the
USAU1 USAU2 system does not
USAU1 USAU2
need to switch.
2. X is configurable,
generally it is
configured as
50% traffic 50% traffic <=50%*number of
MSC/STP SEE nodes of Site A
Scenario 3.1.2: When OCG(SEE) is down (i.e. number of faulty SEE>2) , SEE
Cluster+USAU1 will switch jointly
Site A (Main Site) Connection stopped
BMP BMP Site B
1 3 Connection applied
CBPAdapte
CBPAdapte CBPAdapte
CBPAdapte
rr rr
GMDB GMDB
Automatic switchover
decision mechanism:
SEE SEE SEE SEE SEE SEE SEE SEE SEE SEE 1. In case the number
of SEE where
exception happens
reaches X, the
USAU1 USAU2 system does not
USAU1 USAU2
need to switch.
generally it is
configured as
50% traffic 50% traffic <=50%*number of
MSC/STP SEE nodes of Site A
 USAU+OCG(SEE) are deployed in one DR switch group.
Scenario 3.1.2: OCG(SEE)+USAU GDR switchover
flow
GDR switchover duration: <13s
System
switch System recover
Single Signaling/IP
node links takeover
failure
Time
Disaster detection System Signaling schedule
switch takeover
(About less (About
In case of Manual than 3s) less than
Switch: Depending 10s)
on decision
mechanism; 1. Notify BMP that Depend on STP’s ability, STP
In case of Automatic SEE is down. needs to send charging
Switch: requests to USAU in site B,
Configurable, about that is STP-USAU-SEE-
10minutes CBPAdapter.
Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number of faulty
BMP<=1), no need to switch
Suppose there are multiple BMPs(e.g. BMP1-3) in BMP Cluster 1 in main site, and only BMP1 is down, then BMP2 and
BMP3 can takeover the services, and GDR switch is not required. The mechanism is similar to that of SEE.
BMPGatew
BMPGatew BMPGatew
ay
ay
Site A (Main Site) ay Site B Production
BMP BMP business flow
1 3 DR business flow
w, r w, r w,r Data replication
w, r BMPD BMPD
B B
USRDB USRDB
Switchover decision
GMDB GMDB mechanism:
1. In case the number
of BMP where
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4 exception happens
BillDB BillDB reaches X, the
system does not
CBPAdapte CBPAdapte need to switch.
CBPAdapter CBPAdapter
r 1r 2r r
GMDB GMDB generally it is
configured as
<=50%*number of
BMP nodes of Site A
SEE SEE SEE SEE
Scenario 4.2: When BMP Cluster 1is down, BMP Cluster
1+BMPDB1+BMPGateway will switch jointly
Because BMPDB(SYSDB) forms a complete data, and BMP at each site talks to BMPDB(SYSDB) on that site only, so BMP
Cluster 1 and BMPDB(SYSDB) need switch jointly. BMPGateway is also included in the DR switch group. Connection stopped
BMPGatew Connection applied

BMPGatew BMPGatew
ay
ay
w, r w, r w, r w,r Data replication
w, r BMPD BMPD
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r 1r 2r r
GMDB GMDB
SEE SEE SEE SEE
 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

Scenario 4.3: When BMPDB1 is down, BMP Cluster 1+BMPDB1+BMPGateway will
switch jointly
Because BMPDB(SYSDB) forms a complete data, and BMP at each site talks to BMPDB(SYSDB) on that site only, so BMP
Cluster 1 and BMPDB(SYSDB) need switch jointly. BMPGateway is also included in the DR switch group. Connection stopped
BMPGatew Connection applied

BMPGatew BMPGatew
ay
ay
w, r w, r w, r w,r Data replication
w, r BMPD BMPD
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r 1r 2r r
GMDB GMDB
SEE SEE SEE SEE

Scenario 4.4: When BMPGateway is down, BMP Cluster 1+BMPDB1+BMPGateway
will switch jointly
CRM/ESB is assumed to send all requests to BMP Cluster 1 in site A via BMPGateway1. When BMPGateway is down,
CRM/ESB needs to change BMPGateway IP address to BMPGateway of site B. Connection stopped
Connection applied
Production
CRM/ES business flow
B DR business flow
Data replication
100% traffic
100% traffic
BMPGatew
BMPGatew BMPGatew
Site A (Main Site) ay
ay ay Site B
BMP Cluster 1 BMP Cluster 2

BMP BMP
1 3
w, r w,r
BMPD BMPD
B B

Scenario 4: BMP Cluster 1+BMPDB1+BMPGateway GDR switchover flow
GDR switchover duration: 3m-8m

Service
takeover System recover
Single Dual cluster
node Peripheral
switch element
failure failure switch
Time
Dual cluster Disaster System Peripheral schedule
switch detection switch element switch
(About less (About less than
than 3m) 5m)
In case of Manual 1. Start the application in CRM/ESB needs to change BMPGateway IP
Switch: Depending the DRBMPAPP. address to BMPGateway of site B. (manual
on decision 2. Oracle take over(1-3m). configuration, depending on CRM/ESB’s
mechanism; 3. The GDR software:
 Notify CBPs of site A to
capability)
In case of
Automatic Switch: change BMP Cluster IP
Configurable, address to BMP Cluster
about 10minutes of site B.(auto)
 Notify OCGs of site A to
change BMP Cluster IP
address to BMP Cluster
of site B.(auto)
Summary Table of Switchover Duration of Different
Scenarios
Scenario Switchover Duration Remark

Scenario1: When CBP (APP2) is down 3s
Scenario2: When CBP Adapter1 down 10s
Scenario 3.1.1: When OCG(SEE) down(<=X) 0s no need to switch
Scenario 3.1.2 : When OCG(SEE) down(>X) 13s
Scenario 4: 3m-8m CRM/ESB needs to change
BMPCluster+BMPDB+BMPGateway GDR BMPGateway IP address to
switchover flow BMPGateway of site B, the
duration depends on CRM/ESB’s
capability, we assume it can be
finished in 5m
Data Loss - Oracle Physical DB
Redo Log Data loss: = Data latency * Network efficiency
The data is replicated to the disk and (WAN:0.4 ) * Broadband width (e.g. 10000 Mbps).
redundancy node near real time. The Data latency: < 1-2s, generally less than 100 ms.
latency depends on network
efficiency.
During switchover, the redo log will be uploaded to DB and
No Data Loss.
BMP Production Node BMP Redundancy Node
Active
Active (Read-
write )
Physic Redo
al DB Log
Disk Disk
Data Loss - GMDB (i.e. CBP memory database )
Data Loss = from GMDB to Buffer (< 1MB)+ Buffer to
Every 1s or 1M bytes data, buffer Redundancy Node.
sends data to standby host / disk / Buffer to Redundancy Node = Data latency * Network
redundancy node. The copy speed
depends on network efficiency.
efficiency (WAN:0.4 ) * Broadband width (e.g. 10000 Mbps).
Data latency: < 1-2s, generally less than 100 ms.
CBP/CBPAdapter Production Node CBP/CBPAdapter Redundancy Node
Active Standby Standby
Buffer
GMDB (Log)
Disk Disk
Performance Impact
 CBPAdapter: The AA system performance impact is estimated around 15% compared with without DR
solution.
 CBP: The AA system performance impact is estimated around 15% compared with without DR solution.
 OCG(SEE): The AA system performance impact is estimated around 15% compared with without DR solution.
 BMP: The AS system performance impact is estimated around 10% compared with without DR solution.
Requirement on Dimensioning
For A-A DR solution,

1. License for Oracle GoldenGate is needed for physical DB, including BMPDB(SYSDB), USRDB, CDRDB,
BillDB.
• This data replication software allows physical DB in DR site to be opened read-write while
synchronization occurs. But currently, the physical DB in DR site keeps read only.
• It allows one way data replication and two-way data replication.
• It provides scheme based data replication, that is, one DB can be divided to two schemes and for each
scheme, one way or two way data replication is adopted.
• Huawei CBS 5.5 adopts scheme based one way data replication. But currently, one DB just have one
scheme.
2. The bandwidth needs recalculation.
Thank you
www.huawei.com
Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the
future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could
cause actual results and developments to differ materially from those expressed or implied in the predictive statements.
Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei
may change the information at any time without notice.

Huawei CBS A A GDR Solution PDF

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

Huawei CBS A A GDR Solution PDF

Uploaded by

Copyright:

Available Formats

Security Level:

Huawei CBS V500R005C30

HUAWEI TECHNOLOGIES CO., LTD.

BMPD BMPD Single-node

GMDB GMDB GMDB GMDB Peer to peer

SEE SEE SEE SEE

2. Calling & Data Usage & Other Service

CBP: Convergent Billing Point

GMDB: General Memory Database

OCG: Online Control and Charging Gateway

SEE: Service Execution Environment

Site A (Main Site) Site B

App Standby app

Site A (Main Site) BMP BMP Site B Single-node

3. Update (remote change)

GMDB GMDB GMDB GMDB

MSC STP USAU1 SEE SEE USAU2 SEE SEE

GDR switchover duration: 3s

In case of Manual The GDR software:

SEE SEE SEE SEE

In case of Manual The GDR software:

 USAU+OCG(SEE) are deployed in one DR switch group.

BMPGatew Connection applied

SEE SEE SEE SEE

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

BMPGatew Connection applied

SEE SEE SEE SEE

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

BMP Cluster 1 BMP Cluster 2

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

GDR switchover duration: 3m-8m

Scenario Switchover Duration Remark

BMP Production Node BMP Redundancy Node

CBP/CBPAdapter Production Node CBP/CBPAdapter Redundancy Node

Active Standby Standby

For A-A DR solution,

Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved.

You might also like