Huawei CBS a-A GDR Solution

7/17/2019 Huawei CBS a-A GDR Solution

http://slidepdf.com/reader/full/huawei-cbs-a-a-gdr-solution 1/33

HUAWEI TECHNOLOGIES CO., LTD.

Huawei CBS V500R005C30

Active-Active Disaster Recovery Solution



A-A DR Architecture

Deployment

Data Replication

Solution and RTO for different scenarios in case disaster strikes

Data loss

Impact on Performance and Dimensioning

Contents



HUAWEI TECHNOLOGIES CO., LTD. Huawei proprietary. No spread without permission. Page 4

USAUUSAU FEPFEP

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB

Site A (Main Site) Site B

CBPAdapter1

GMDB

SEE SEE SEE SEE

FEP/

GFEPFEP/GFEP

BMP

BMPDB

BMP

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USAU1 USAU2

MSC/STPGGSN/

PGWSMSC MMSC

Core Network

Active-Active DR Architecture – High Level

CDRDB

USRDB

GMDBGMDB GMDBGMDB

DCC

CAP/MAP/INAPSMPP+

EMPP

CDRDB

USRDB

If SMSC/

then SM

directly.

BillDB BillDB




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 tran

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 physica

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, t

synchronized from GMDB of site A to GMDB of site B or vice versa, depending on which site receive and p

b. When the CBP updates the GMDB and these updates need to be written to physical database. No ma

processes the traffic, the updates will first synchronized to physical database of site A and then written to




Acronyms

BMP: Business Management Point

In the Huawei OCS solution, the BMP implements service operation management, and provide system ma

management, Offer Management, resource management, customer management & customer service Ma

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 o

For online charging, after receiving the charging & authentication request from the OCG, the CBP perform

reservation for the conversation duration, and indicates the conversation duration to the OCG. After recei

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 indust

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




BMPGateway

Invoicin

g

USAUUSAU FEPFEP

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB

Site A (Main Site) Site

CBPAdapter1

GMDB

SEE SEE SEE SEE

FEP/

GFEPFEP/GFEP

BMP1

BMPDB

BMP3

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USAU1 USAU2

MSC/STP GGSN SMSC MMSCCore Network

USRDB

GMDB

GMDB

GMDB

GMDB

DCC

CAP/MAP/INAPSMPP+

EMPP

If SMSC/

then SM

directly.

USRDBInvoicin

g

BillMgm

t

Invoi

g

BillM

t

BMPGateway

w, rw, r

CDRDB

BillDB

CDRDB

BillDB

RepoReport

Mediation

I200I2000

Median

r r

BMPGatew

ay




NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma

nual

Remark

CBPAdapter

(incl. GMDB)

A-A Two-node cluster (100% capacity,

50% production traffic)

Two-node cluster (100% capacity,


Both GMDB in site 1/2 is div

each scheme adopts o

CBP (incl.

GMDB)

A-A Two-node cluster (100% capacity,




Both GMDB in site 1/2 is div

each scheme adopts oUSAU A-A Two-node cluster (100% capacity,




Both No date replication

FEP/GFEP A-A Two-node cluster (100% capacity,




Both No data replication

1，Depends on wheth

polling mode.

SEE (i.e. OCG) A-A N+1 cluster (load balancing,

100% capacity, 50% production

traffic)

N+1 cluster (load balancing,

100% capacity, 50% production

traffic)

Both In case N=1, Site 1/2 will

In case N>=2, Site 1/2 wi

enough because N provid

traffic is handled)

BMPGateway

(SLB)

A-S Two-node cluster (100% capacity,


Single-node system (100%

capacity, 0% production traffic)

Both No date replication

BMP A-S N+1 cluster (100% capacity,


N+1 cluster (100% capacity, 0%

production traffic)

Both Including UPC/GL/AR/

BMPDB(SYSD

B)

A-S Two-node cluster (100% capacity,

100% production read traffic,

100% production write traffic)


capacity, 0% production read

traffic, 0% production write traffic)

Both Oracle Active Data Gu

DR Deployment Scheme -1/2




NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma

nual

Remark

USRDB A-S Two-node cluster (100% capacity,

100% production read traffic,

100% production write traffic)


capacity, 0% production traffic)

Both

CDRDB, BillDB A-S Two-node cluster (100% capacity,100% production traffic) Single-node (100% capacity, 0%production traffic) 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%

production traffic)

Both

Bill

Management

A-S Single-node (100% capacity,



production traffic)

Both

Report A-S Single-node (100% capacity,



production traffic)

Both By default, DR is not s

In case of DR, only rep

source file will not be r

Mediation A-S Single-node (100% capacity, 50%

production traffic)

Single-node (100% capacity,


Both No date/file replication

I2000 A-

S(Optio

nal)

Two-node cluster or single-

node(100% capacity, 100%

production traffic)


production traffic)

Both If I2000 is deployed in

then DR is not suppor

If I2000 is deployed in

DR can be supported,

single-node in DR site

DR Deployment Scheme- 2/2 (End)




Oracle GoldenGate Data Replication

OG

Ora

Trail filesTrail files

1. The Oracle Golde

source DB extrac

and archive log a

local trail file.

2. OGG sends the t

source DB to targ

3. The OGG of the t

file content and

the target DB to

Source

Oracle DB

Target

Oracle DB

Online

redo logs

Archived

redo log

files


2.1 Send

1, Extract

Network2.2 Receive

3, Apply




For BMPDB/USRDB , Huawei use Oracle DB, the Replication solution will use Oracle Golden Gate. License fee needs to b

BMPGateway + BMP+BMPDB are deployed in one DR switch group.

Date Replication for BMPDB and USRDB

BMPDB

BMP1

BMPDB

BMP3

(Read-write

status)

(Read-only

status)


USRDB USRDB

Write, read

(Read-write

status)

(Read-o

status)

readCach

ewrite

Cach

e

CBP4CBP3CBP2CBP1 CBP2CBP1 CBP4CBP3

GMDB

GMDB

GMDB

GMDBrCache

write

Cache

write

Cache

Cacher r

write

r

write

SEE SEE SEE SEE

r r

Cache Cache CacheCache

Date Replication for USRDB Low Level : Asynch




Date Replication for USRDB –

Low Level : Asynch

Replication

Site A Active

Site B Active

USRDB USRDB2. Send change

3. Update (remote change)

1. Update

1. Update

replication engine

3. Update (remote chang

Application Application

To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication

The related application includes BMPAPP, CBPAPP.




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 – High Level

CBP4CBP3CBP2CBP1 CBP2CBP1 CBP4CBP3

GMDB

GMDB

GMDB

GMDB

CBPAdapter

CBPAdapter

CBPAdapter

1 GMDB

CBPAdapter

2GMDB

Date Replication for GMDB Low Level : Asynchr




Site A Active

Site B Active

GMDB GMDB2. Send change

3. Update (remote change)

1. Update

replication engine

3. Update (remote chang

Scheme2b

Scheme1a

Scheme2a

Scheme

1b

Application Application

To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication

The related application includes CBPAPP, CBPAdapter

Date Replication for GMDB –

Low Level : AsynchrReplication




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 CB

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

based routing will be applied.

Routing

135* 138* 135* 138*

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

CBPAdapter1

GMDB

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

GMDBGMDB GMDBGMDB




SEE cluster in both sites share the same Virtual GT (GT3). SEE cluster in site A has a real GT(GT1), SEE clu

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 onl

Virtual GT of OCG(SEE)

MSC STP USAU1 SEE SEE USAU2

IDP(DGT=GT3)IDP(DGT=GT3)

RRBE(OGT=GT1)RRBE(OGT=GT1)

ERB(DGT=GT1)ERB(DGT=GT1)

IDP(DGT=GT3)

RRBE(OGT=GT1)

ERB(DGT=GT1)

IDP(DGT=GT3)IDP(DGT=GT3)

IDP(DGT=GT

RRBE(OGT=GRRBE(OGT=GT2)

RRBE(OGT=GT2)




Scenario1: When CBP (APP2) is down

1. D

bC

2. W

ts

t

i

i

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB


CBPAdapter1

GMDB

SEE SEE SEE SEE

BMP1

BMPDB

BMP3

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USRDB

GMDB

GMDB

GMDB

GMDB

USRDB

rww, rw, r r

CDRDB

BillDB

CDRDB

BillDB




Scenario1: CBP GDR switchover flow

Single nodefailure

Dual clusterswitchfailure

Dual clusterswitch

Disasterdetection

System switch（ About less than 3s）

Timeschedule

System

switch

Servicetakeover

In case of Manual

Switch: Depending

on decision

mechanism;In case of

Automatic Switch:Configurable,

about 10minutes

RTO/Downtime：

3s

The GDR software:1. Check the CBP data replication link, if it is not

stopped, stop it.2. Set the CBP2 status to faulty in system

definition table in BMPDB(SYSDB), update thestatus of CBP2 into the cache of other normalCBPs and CBPAdapter. Then CBPAdapterautomatically change routing.

GDR switchover duration: 3s




Scenario2: When CBP Adapter1 is down

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1


CBPAdapter1

GMDB

SEE SEE SEE SEE

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

GMDB

GMDB

GMDB

GMDB

MSC/STP GGSN SMSC MMSCCore Network

DCC

FEPFEPFEP/

GFEPFEP/

GFEP

SMPP+

EMPP

S i 2 CBP Ad R i Fl




Scenario 2: CBP Adapter Rerouting Flow

Single

nodefailure

Dual cluster

switchfailure

Dual clusterswitch

Disasterdetection

Rerouting (Aboutless than 10s）

Systemswitch

Servicetakeover

In case of Manual

Switch: Dependingon decisionmechanism;

In case of AutomaticSwitch:

Configurable, about

10minutes

RTO/Downtime： 10s

The GDR software:

1. Check the CBPAdapter data replication link, if it isnot stopped, stop it.

2. Set the CBPAdapter1 status to faulty in systemdefinition table in BMPDB(SYSDB), update the

status of CBPAdapter1 into the cache of every CBPand SEE. Then SEE automatically change routing.

SEE automatically set the CBPAdapter1 status to

faulty and will not send requests to CBPAdapter1.

GDR switchover duration: 10s

Timeschedule

Scenario 3 1 1: When OCG(SEE) is down (i e number of faulty SEE




USAU2USAU1

CBPAdapter

CBPAdapter

Scenario 3.1.1: When OCG(SEE) is down (i.e. number of faulty SEE

to switch

USAU2

SEE SEE

USAU1

SEE SEESEE

CBPAdapter

GMDB

CBPAdapter

GMDB

Site A (Main Site)

MSC/STP

50% traffic 50% traffic

BMP1

BMP3

SEE SEE SEE SEESEE

Site B





USAU2USAU1

CBPAdapter

CBPAdapter

USAU2

SEE SEE

USAU1

SEE SEESEE

CBPAdapter

GMDB

CBPAdapter

GMDB


MSC/STP

50% traffic 50% traffic

BMP1

BMP3

SEE SEE SEE SEESEE


Cluster+USAU1 will switch jointly

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

Scenario 3 1 2: OCG(SEE)+USAU GDR switchove




Singlenode

failure

Signaling/IPlinks takeover

System recover

Disaster detection Signalingtakeover(About

less than10s)

Timeschedule

Systemswitch

Systemswitch

(About lessthan 3s)

Depend on STP’s ability, STPneeds to send chargingrequests to USAU in site B,

that is STP-USAU-SEE-

CBPAdapter.

GDR switchover duration: <13s

Scenario 3.1.2: OCG(SEE)+USAU GDR switchoveflow

1. Notify BMP that

SEE is down.

In case of Manual

Switch: Dependingon decisionmechanism;

In case of AutomaticSwitch:

Configurable, about

10minutes

Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number o




Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number o

BMP<=1), no need to switchSuppose 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.

BMPGateway

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB


CBPAdapter1

GMDB

SEE SEE SEE SEE

BMPDB

BMP

3

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USRDB

GMDB

GMDB

GMDB

GMDB

USRDB

BMPGateway

w,rw, rw, r

w, r

CDRDB

BillDB

CDRDB

BillDB

BMPGateway

r r

BMP

1

Scenario 4.2: When BMP Cluster 1is down, BMP Cluster




,

1+BMPDB1+BMPGateway will switch jointlyBecause 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.

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

BMPGateway

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB


CBPAdapter1

GMDB

SEE SEE SEE SEE

BMPDB

BMP

3

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USRDB

GMDB

GMDB

GMDB

GMDB

USRDB

BMPGateway

w,rw, rw, r

w, r

CDRDB

BillDB

CDRDB

BillDB

BMPGateway

r r

BMP

1w, r

Scenario 4.3: When BMPDB1 is down, BMP Cluster 1+BMPDB1+B




,

switch jointlyBecause 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.


BMPGateway

CBPAdapter

CBPAdapter

CBP4CBP3CBP2CBP1

BMPDB


CBPAdapter1

GMDB

SEE SEE SEE SEE

BMPDB

BMP

3

CBP2CBP1 CBP4CBP3

CBPAdapter2

GMDB

USRDB

GMDB

GMDB

GMDB

GMDB

USRDB

BMPGateway

w,rw, r

CDRDB

BillDB

CDRDB

BillDB

BMPGateway

r r

BMP

1w, r w, rw, r

Scenario 4.4: When BMPGateway is down, BMP Cluster 1+BMPDB




y

will switch jointly

BMPGatewaySite A (Main Site) Site B

BMP1

BMP3

BMPGateway

BMPGatew

ay

CRM/ESB

BMPDB

BMPDB

100% traffic

w,rw, r

BMP Cluster 1 BMP Cluster 2

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.


100% traffic

Scenario 4: BMP Cluster 1+BMPDB1+BMPGateway GDR switchov




Singlenode

failure

Dual clusterswitchfailure

System recover

Dual clusterswitch

Disasterdetection

Timeschedule

Servicetakeover

Peripheralelementswitch

Scenario 4: BMP Cluster 1+BMPDB1+BMPGateway GDR switchov

CRM/ESB needs to change BMPGatewaddress to BMPGateway of site B. (configuration, depending on CRM/E

capability)

Peripheralelement switch(About less than

5m)

GDR switchover duration: 3m-8m

1. Start the application inthe DRBMPAPP.

2. Oracle take over(1-3m).

3. The GDR software:

Notify CBPs of site A tochange BMP Cluster IP

address to BMP Cluster

of site B.(auto)

Notify OCGs of site A to

change BMP Cluster IP

address to BMP Clusterof site B.(auto)

Systemswitch

(About lessthan 3m)

In case of ManualSwitch: Dependingon decision

mechanism;In case of

Automatic Switch:

Configurable,

about 10minutes

Summary Table of Switchover Duration of Different




Scenario Switchover Duration Remark

Scenario1: When CBP (APP2) is down 3sScenario2: 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:

BMPCluster+BMPDB+BMPGateway GDR

switchover flow

3m-8m CRM/ESB needs to c

BMPGateway IP ad

BMPGateway of sit

duration depends ocapability, we assum

finished in 5m

yScenarios




Active

Redo

Log

Physic

al DB

The data is replicated to the disk and

redundancy node near real time. Thelatency depends on network

efficiency.

Redo Log Data loss: = Data latency

(WAN:0.4 ) * Broadband width (e.g.

Data latency: < 1-2s, generally less t

During switchover, the redo log will bNo Data Loss.

Disk Disk

Active(Read-write )

Data Loss - Oracle Physical DB

BMP Production Node BMP Redundancy Node




Data Loss - GMDB (i.e. CBP memory database

Standby Active

Buffer

(Log)

Standby

GMDB

Every 1s or 1M bytes data, buffer

sends data to standby host / disk /redundancy node. The copy speed

depends on network efficiency.

Data Loss = from GMDB to Buffer (<

Redundancy Node.

Buffer to Redundancy Node = Data

efficiency (WAN:0.4 ) * Broadband w

Data latency: < 1-2s, generally less t

Disk Disk

CBP/CBPAdapter Production Node CBP/CBPAdapter Redundancy




Performance Impact

CBPAdapter: The AA system performance impact is estimated around 15% compared with

solution.

CBP: The AA system performance impact is estimated around 15% compared with without

OCG(SEE): The AA system performance impact is estimated around 15% compared with wit

BMP: The AS system performance impact is estimated around 10% compared with without




Requirement on Dimensioning

For A-A DR solution,

1. License for Oracle GoldenGate is needed for physical DB, including BMPDB(SYSDB), USRD

BillDB.• This data replication software allows physical DB in DR site to be opened read-write whil

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 scheme

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 ju

scheme.

2. The bandwidth needs recalculation.



Thank youwww.huawei.com

Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved. The information in this document may contain predictive statements including, without limitation, statemefuture financial and operating results, future product portfolio, new technology, etc. There are a number of cause actual results and developments to differ materially from those expressed or implied in the predTherefore, such information is provided for reference purpose only and constitutes neither an offer nor an amay change the information at any time without notice.

Huawei CBS a-A GDR Solution

Documents

Transcript of Huawei CBS a-A GDR Solution