104215649 lecture cbs of huawei july2012(1)

1 | P a g e C o v e r g e n t B i l l i n g S y s t e m o f H u a w e i ( S u m m a r y )

Covergent Billing System ( CBS ) Summary

22 July 2012

By Asif Rahman Saikat

Huawei’s OCS is a next generation charging system, which provides the convergent charging capability,

such as: prepaid /postpaid convergent rating, voice service/data service convergent, multi network

convergent

Fig: System Architecture

Huawei OCS is composed of 3 functional layers: Service Management Layer, Service Data and

Rating Layer, and Service Control Layer.

Service Management Layer: including BMP providing Account Balance Management, Subscriber

Management、Pricing Management, I2000 working as EMS, RPTS supporting reports and Bill

Server for call detailed information query.

Product

CatalogMarketing Customer Care

Service Data and

Rating Layer

MSC/SSP SGSN/GGSN

Core Network and Service Enabler

CRM

Service Management

Layer

Service Control

Layer

SMSC/MMSC…

IVR OCG FEP

Convergent Rating

Credit Control Bonus

UVC

CBP

Account Balance

Management

Subscriber

Management

Pricing Management

Huawei OCS

BMP

I2000 RPTSBill

Server


Service data and Rating Layer: In this Layer, the OCS provides rating, charging and accounting

functionality, and supports both online/offline charging and prepaid/postpaid charging.

Service Control Layer: The Layer includes OCG, FEP. OCG complete the access control(such as

voice, sms, data etc.). FEP works as a protocal adaptor or as OCS invoked SMS deliver.

The components in Service Control Layer include OCG, FEP,IVR.

Network Element FUNCTIONS DESCRIPTION

OCG

( Open Charging Gateway )

Open Charging Gateway

OCG (Open Charging Gateway) is a high availability platform which handles the service control, processing, and traffic management with INAP/CAP/WIN.

It interacts with CBP though DCC interface to authenticating subscriber and applying for the call time when it receive a call.

At the end of the call, OCG will report the call duration time to CBP and request CBP for charging.

FEP Front End Processor

FEP (Front End Processor) is also an interface entity between the OCS system and 3rd party systems such as banks, SMSC (Short Message Service Center), etc. to accomplish the conversion between different protocols so as to extend the functions of the OCS system. Notification SMS invoked by OCS will deliver to FEP for sending.

URP Universal Resource Platform

The U-SYS Universal Resource Platform (URP8100 for short) is used for both narrowband and broadband media resources. Inheriting all features of C&C08-AIP, the URP8100 is an intelligent peripheral of media resources in next generation network (NGN).

The URP8100 uses industry-leading software and hardware architecture, featuring large capacity, high integration, rich media resources, and strong service support. It also enjoys powerful networking ability by supporting PSTN/PLMN and NGN. (In this project, it will not use Huawei URP, it use current IP in MSC/SSP)

Table : The components in Service Control Layer include OCG, FEP,IVR.

Service data and Rating Layer

The Service data and Rating layer in the above figure is composed of CBP. The main function of

each module/subsystem is listed as below:


CBP Convergent Rating & Charging

CBP is the core module in Huawei OCS, providing unified rating & billing engine and supports both online charging and offline charging.

The services cover voice, SMS, data service (volume and


duration based), content. Also include periodic charging such as monthly rental, rebating, bonus, and discount.

CBP accumulates usage real-timely and generates rated CDRs for future query.

Generates Rated CDR.You can

collect CDR from there and check

the charging is ok or not and also

can check is it is being using the

proper Product Key.

Credit Control The real-time balance & account management and credit control for prepaid subscribers and postpaid subscribers is in CBP.

UVC Voucher Center

UVC consists of UVC (Uniform Voucher Center) and CMP (Card Management Point).

The UVC is mainly used to store voucher cards related data, and handle the recharge request from subscriber.

CMP is mainly in charge of the centralized management over the card data creation, loading-to-database, deletion, activation/deactivation, locking/unlocking and query of the recharge card data file.

Service Management Layer include BMP and IVR. The main function of each module/subsystem is

listed as below:


BMP

Account Balance Management

Account Balance Management manages one or

more account balances for a subscriber or group of

related subscribers, for example for a family.

Account balances can be prepaid, postpaid or

hybrid models with allowances for particular

services.

Subscriber Management

Subscriber Management provides

create/delete/input customer information, service

ordering information, blacklist management,

Customer Relationship Management.

Pricing Management

Pricing Management operator to define product

and manage service. Products have been

categorized into: main products, group products,

appendent service products and appendent tariff

products.Appendent product have higher priority

than Main product.And system always choose the


LOWER price in case of charging.

I2000 Monitoring and Maintenance

I2000 (iManager 2000) is a unified NMS (Network Management System) of Huawei OCS. It provides statistics of performance and monitoring, alarm management, operation and maintenance of all elements. The statistic result of service traffic also generated by I2000. I2000 provides SNMP interfaces to the superior NMS.

RPTS Intelligent Report System

RPTS is a Web-based system. It allows you to design reports based on a template, create, distribute, and manage reports based on the Web, create manual and schedule reports.

Bill Server CDR Query Bill Server system store call detailed records and provide query function.

AREA Interfaces With

Objects

IN Remark

VOICE GSM MSC/SSP Base on CAMEL II


IP Base on CAMEL II

PTP SMSC SMPP+ -> FEP -> SCP

MMSC MMSC -> MDSP -> SCP

PTA SMS PTA SMSC -> MDSP -> SCP

MMS PTA MMSC -> MDSP -> SCP

DATA GPRS Based on CAMEL 3 by SGSN

Content Download SP/WAP -> MDSP ->SCP

RBT RBT Download, Rent

(MML)

RBT->FEP->SCP, RBT->SMP

Notification SMC SCP->FEP->SMC

Recharge Voucher IVR->SCP

SMS->GFEP->SCP (currently not

used)

USSD->HLR->SCP

ELOAD DEALER -> EVC -> SMP -> SCP

Balance

Transfer

Balance SMSC -> SCP

USSD ->HLR -> SCP

IVR -> MSC ->SSP

3rd Party -> SMP

Query Profile/Balance SMSC -> SCP (currently not used)

USSD ->HLR -> SCP

IVR -> MSC ->SSP->SCP

Service

Operation

FNs

BA

Ecare

MML


Figure :: Target Network Architecture of Huawei OCS

1. One centralized BMP is deployed to support 25 M subscribers, which will manage all the OCS

OCG & CBP nodes in 2 production sites. This scheme will be helpful to reduce OPEX.

2. OCG and CBP are deployed in two production sites with site1 supporting 14 M subscribers and

site2 supporting 11M subscribers.

3. BMP adopt 1+1 DR mode, one product site and one DR site. OCG & CBP adopt 2+1 DR mode, site

1 & site 2 are production site, site 3 is the DR site, which means one DR site 3 will take over the

traffic from production site1 or production site 2, according to which site will happen disaster

firstly. The DR site 3 synchronizes all the data from site 1 & site 2, and the synchronized data

from site 1 & site 2 is back up in different volume in site 3 DB.

4. Because each site has 5~6 clusters of active-standby CBP’s, and in order to simplify the

connection between CBPs and VAS entities, DCCPROXY is introduced to provide single access

point for VAS entities (GGSN, CRBT and 3rd party applications), which talk to OCS through

Diameter interface. That will be easy for network management and maintenance.

5. For reliability & avoid long distance diameter connection between DCC Proxy and CPBs, for each

site will deploy one DCCPROXY. DCCPROXY in each site is furnished with dual-cluster system to

meet high reliability requirement.


6. OCS system adopts IP in SSP throughout the core network for playing announcement. It’s same

as Legacy IN solution. All announcements of OCS service will be loaded in all SSP/IP. The existing

AIP/URP will not be reused for OCS.

Fig : Interfaces between Huawei OCS and External Systems

A-END System B-END System Protocol Role

CRM/CC/FNs/BA

/Ecare… OCS BMP

Web

Service

Service operation and reverse work

order for service provisioning

OCS CBP Billing sFTP/FTP CDR transfer

MDSP OCS GFEP RTBP P2A SMS, A2P SMS, MMS and Content

Download charging

SMSC OCS GFEP SMPP 3.4

System Notification and self care via

SMS such as balance transfer,

profile/balance query

SMSC OCS GFEP SMPP+ P2P SMS rating and charging

CRBT OCS DCC Proxy DCC CRBT download fee, rental fee charging

GGSN OCS DCC Proxy DCC

GPRS service rating and charging

(Notes: It can support charging by URL

which is more flexible than CAP3. The

DCC based GPRS charging will be used


after the migration)

SGSN OCS OCG CAP 3

GPRS service rating and charging

(Notes: It is only used during the

migration in order to guarantee the

network stable)

MSC/SSP/AIP OCS OCG CAP 2

Voice service rating and charging, self

care via IVR such as balance transfer,


HLR OCS OCG MAP

System notification and self care via

USSD such as balance transfer,


UVC OCS OCG INAP Voucher card recharge

ELoad DCC Proxy DCC Electronic recharge

3rd Party APP,

e.g. SCL, MCN,

MOD etc

DCC Proxy DCC 3rd party application charging

I2000 NMS SNMP

Report alarm information, performance

information, and configuration

information to superior NMS


Only prepaid calls shall be triggered to OCS and be charged online. Later for CBS, all calls include

prepaid, postpaid & hybrid should be triggered to OCS.

MSC/SSP communicates with OCS based on CAP2, MSC/SSP send the CAP

message to USAU (Universal signal access point), UASU send to OCG for call

control, OCG send diameter message to CBP for authentication and charging.

(NB::ASIF::USAU+SCP==OCG)

The charging request is sent from SMSC to OCS for P2P SMS through SMPP+ interface.

Rating and charging is done by OCS. The price of P2P SMS is configured through OCS SMAP.

During migration, SMSC connect to IN and OCS respectively through SMPP+ interface according to

number segment.


The charging request is sent from GGSN to OCS for GPRS through DCC interface.

During the migration, the GPRS rating and charging will still be from SGSN to OCS through CAP3

interface, same as existing IN solution.

The charging request is also sent from CRBT to OCS for dowloand fee and subscription fee through

DCC interface.

During migration, the rating will still be done by CRBT same as exising IN solution, and OCS is

responsible for fee deduction. CRBT send charging request to IN through MML and to OCS

through DCC respectively according to number segment.


As there will be centralized Customer Care/Provision which will provide unified access for VAS

services and unified provision to NEs including OCS, HLR, VAS platform such as CRBT, so the rating

and charging of CRBT subscription fee will be fully done by OCS. CRBT is only responsible for the

management of the SP/CP/service and assign the content ID. The product and price of CRBT

subscription fee will be configured manually in OCS.

Voucher card recharge has IVR, SMS, and USSD three ways.

Electronic recharge is from ELoad to OCS through DCC interface.


During migration, Eload communicate with IN and OCS by MML according to number segment.

After the migration, the ELoad need upgrade to support DCC to integrate with OCS.

How to do the Prepaid Subscriber Provision

1. Operator creates the provisioning files for prepaid subscribers in single/batch

mode.

2. Operator login OCS SMAP, upload the provisioning files and start to provision

prepaid subscribers in OCS.

3. OCS talks to HLR to finish the provisioning on HLR through MML. All OCS services

will be pre-activated in HLR. (Whether this step is included depends on the

configuration, if this step is not needed, the provisioning in HLR will be

independently through the HLR SMAP by manual.)

4. OCS feedback the response in provisioning result files to operator. If there is any

provisioning failure in OCS or HLR, it will be corrected by manual.


How in CBS , Prepaid Subscriber Provision (In Phase II CBS Solution)

1. Customer Care sends the prepaid creation request to BMP, the request can be

Single/Batch.

2. BMP Create prepaid profile and response back to Customer Care.

3. Customer Care sends to Provisioning System for Prepaid activation. The request

can be Single/Batch.

4. Provisioning system sends creation request to HLR only for prepaid lines, one by

one.

5. HLR responses back to Provisioning.

6. Provisioning system sends the response back to Customer Care.

First Call Activation for Prepaid


1. On user First Call, MSC triggers OCS System.

2. OCS updates the subscriber status and returns the welcome voice ID for announcement.

3. MSC/IP prompt welcome message to the user.

4. OCS sends the welcome SMS message to user via SMSC.

Voice Service

1. GSM calling flow

MSC/VLR SCP GSM

Signalling ISUP

Signalling CAP

REL

RLC

CBP

ERB

RC

This area is repeatable

ACR

AC

HLR

Signalling MAP

CCR {Initial}

CCA {Initial}

Authentication

inverse calculation

reserving fees

Number analysis

IDP(MO)

RRBE

AC

FCI

Continue

IAM (PSTN number)

ACM

ANM

ACR

CCR {Update}

CCA {Update}

CCR {Terminate}

CCA {Terminate}

Rating,

Debiting accounts,

Reserving fee

Rating,

Debiting accounts,

ending sessions

Trigger by

O_CSI

1. Calling user initials a call, MSC/VLR sends an IDP message to SCP, in this message contains the

location information of the calling party and other parameters.

2. SCP receives IDP message from MSC/SSP and return the RRBE message.


3. SCP analysis and process the received number, and checks whether the number is barred or

emergency call, if yes SCP needn’t send request message to CBP.

If the call relates to the service with location charging feature such as local discount charging or

same area bonus, SCP need to send ATI message to HLR to get the called party location.

4. SCP get the subscriber’s home CBP, then send CCR (Initial, RSU (CC-time), Service-ID, IMSI,

Location，etc.) to CBP for authentication and budget.

5. CBP analysis the request message to do authentication, rating, reserving balance, and then

send CCA (Initial, RC=Success, GSU (300S, for example)) with the usable call time to SCP.

6. SCP sends AC, FCI (optional) and Continue messages to MSC/SSP; MSC/SSP executes call

monitor.

7. After the call is connected according to the called number contained in the IAM message and

the conversation reaches the given segment (300S for example), MSC/SSP reports the ACR to

the SCP.

8. SCP receives ACR message from MSC/SSP, and then send CCR (Update, USU (300S)) to CBP to

report the used call time.

9. CBP does calculate and charging the last segment fee according to CCR message, reservation

for the next segment and then send CCA(Update, RC=Success, GSU(300S)) with usable call time

to SCP.

10. When the call is finished, SCP receives ERB and ACR from MSC/SSP and send CCR(Terminate,

USU())to CBP to report the used call time.

11. CBP calculates and deducts the account according to CCR message, and then return CCA

(Terminate, RC=Success) to SCP and end the sessions.

12. The SCP returns RC message to the MSC/VLR, the call ends.

2. GSM called flow


SCP

IDP(MT)

RRBE

AC

Contuinue

Signalling CAP

CBP

Number analysis

CCR{Initial}

CCA {Initial}

Authentication,

inverse calculation,

reserving fees

ACR

CCR{Terminate}

CCA{Terminate}

CCA{Update}Rating, debiting

accounts,

reserving fee

ERB

CCR{Update}

Rating, debiting

accounts, ending

sessionsRC

This area is repeatable

ACR

AC

HLR

SRI

SRI ACK(T_CSI)

Signalling MAP

MSC/VLR

SRI

SRI ACK

Trigger by T_CSI

1. MSC/VLR receives a call, sends an SRI message to the HLR and obtains T-CSI. Then, MSC/VLR

sends an IDP message to SCP, in this message contains the location information of the calling

party and other parameters.

2. After receiving the IDP message, the SCP send RRBE message.

3. SCP analysis the calling and called number, and the SCP authenticate the right of receiving calls of

the called party. If yes, SCP gets the home CBP of the called user and sends the CCR(RSU (CC-

time), Service-ID, IMSI, Location，etc.) message to the CBP.

4. The CBP performs the operations of authentication, inverse calculation, and fee reservation.

Then, the CBP returns the CCA(Initial, RC=Success, GSU (300S, for example)) with the usable call

time to SCP.

5. SCP sends the AC and Continue messages to MSC/VLR, MSC/SSP executes call monitor.

6. After the call is connected, and the conversation reaches the given segment (300S for example),

MSC/SSP reports the ACR to the SCP.


7. SCP receives ACR message from MSC/SSP, and then send CCR (Update, USU (300S)) to CBP to

report the used call time.

8. The CBP performs the operations of rating, debiting accounts, and reserving fees. Then, the CBP

returns the CCA(Update, RC=Success, GSU(300S)) with usable call time to SCP.

9. When the call is finished, SCP receives ACR from MSC/SSP and send CCR(Terminate, USU())to CBP

to report the used call time.

10. CBP calculates and deducts the account according to CCR message, and then return CCA

(Terminate, RC=Success) to SCP and end the sessions.

11. The SCP returns RC message to the MSC/VLR, the call ends.

1.1.1 Unified Service Access Unit & Control (USAU & OCG) The Real Time Billing has the request of real time control for all the service. Huawei adopts the

mature Intelligent Network solution to support the voice/SMS/Data services control.

The OCG (Service Control Point) will use standard protocol to connect with the core network, and

use Diameter protocol to connect with CBP (Convergent Billing Point) to apply the rating/charging

function.

OCG can be divided into two parts: SAU which is responsible for signaling access and SCDU which

is responsible for data manipulate and service control. The structure is shown as below:

SAU is based on Huawei U-SYS® USAU platform. It provides format conversion between SS7 signaling and

TCP/IP based internal message.

Again, SCDU can be divided into two logical entities: SCU and SDU. SCU is responsible for service

control, where service logics are running.

SDU is responsible for data manipulate, where database are running. For small capacity SCU and

SDU coexist in a same server making up of a SCDU. In large capacity, SCU and SDU can run in

independent server. SCU works in N+1 load sharing and SDU works in host-standby cluster mode

which can save the signaling point of OCG.


1.1.1.1 USAU

The USAU provides unique functions in the telecom networks and service capabilities.

As a signaling access unit of telecom devices in the intelligent network (IN), the USAU converts the

signaling protocols between telecom devices, and supports:

The Time Division Multiplex-based (TDM-based) narrowband No.7 signaling network

The Internet Protocol-based (IP-based) broadband signaling transport (SIGTRAN) network

The USAU is based on the open standards telecom architecture (OSTA) platform. The USAU has

high signaling link processing capability and integration degree and provides more powerful

signaling access capability for:

Service control point (SCP)

Home location register (HLR)

Short message service center (SMSC)

The USAU provides the signaling access function for the SCP, SMSC, and the HLR

( Till Page 40 out of 125)


Convergent Charging & Billing Point (CBP)

CBP software architecture

1. CBP receives a call request, this call request has been preprocessed.

2. Service recognition function judge what kind of service the call request is, for example: this call

is mobile originating, domestic toll call, domestic roaming and etc.

3. Authentication function judge whether or not the subscriber has the right to make this call,

according to subscriber properties (e.g. account state, outgoing call permission) and call specific

information (e.g. toll, roaming).

4. Perform pre-calculation according to the account information, call specific information and

product ordering information of the subscriber, work out total call duration the subscriber can

afford. CBP will check all products the subscriber ordered, all the charging strategies and rules, find

out rules which match the call, and perform accurate calculation.


5. Apply to reserve a portion of balance from the related accounts, in case of allowed call duration

is less than predefined time slice (300 seconds in default), all the remained balance will be

reserved.

6. Indicate to connect the call.

7. CBP detects subscriber hang up or time slice has been used up (under CAMEL standard, a

midterm report will be received).

8. Perform post-calculation according to the call duration, call specific information, account

information and product ordering information of the subscriber, work out call cost (may involve

multiple accounts).

9. Accounting/billing function charge the previous call segment from the account, previous

reservation will be committed, call record will be generated.

If the call is still active, CBP will repeat the rating, reservation and accounting processes. Following

this process model, CBP can meet various telecom service charging demands.

1.1.2 Business Management Point (BMP)

BMP is the adapter and interface of management data and service logic, flashing the data from

CC&BM to CBP/OCG, and work order from CBP to CC&BM. The whole service flows such as

creating new subscriber, changing rate plans, changing customer information, also need the help

of BMP as an interface from CC&BM to CBP


OCS USAU has supported all protocols including CAP, WIN, SIP, INAP etc.

OCS OCG can support the SIP access directly without the USAU.

Maintain Engineer can monitor system performance and find abnormal information in time. So

engineer can prevent accident.

Performance item List:

CAPS

Successful Rate Low

CPU Idle

IO Idle

Memory Idle

Response in time rate

( Till Page 82 out of 125 )

1.2 Fault Possibility

Critical faults: MTBF - Mean Time Between Failures > 2000 days

Major faults: MTBF > 1000 days

The MTBF value is estimated according to minicomputer vendor’s information. It may vary under certain

condition.

1.3 Faults Resume Time

It’s cold standby for RAX OCS project. The switchover time of CBP normally is within 5 minutes.


The switchover time of OCG-SDU normally is within 5 minutes, and it will take maximum 10 minutes in extreme situation (in peak time).

Notes:

Fault resume duration above for critical or major faults is achieved by dual-cluster swithover.

For troubleshooting, critical, major and minor all kind of faults will be handled as per AMC between Huawei and RAx.

1.4 Capacity and Performance

1.4.1 Key Performance Index

Maximum number of DCC clients supported by CBP

Each DCC adapter service provides a DCC port, and each port can support maximum 20 DCC clients,

while CBP can start multiple DCC adapter service according to the configuration of CBP server.

Maximum number of Web clients supported by BMP

No application limitation, but limited by memory and JVM memory access limitation. Under 32-bit JVM,

BMP supports maximum 400 concurrent clients access, and 2000 under 64-bit JVM.

Maximum number of operators supported by BMP: 1000

Maximum OPS (Operations Per Second) supported by BMP

Single BMP can handle maximum 100 non-batch operations per second, while actual supported OPS

depend on the hardware equipment.

Maximum number of subscribers supported by single CBP

5,000,000 subscribers, actual capacity depends on the hardware configuration.

Maximum number of subscribers supported by single BMP

5,000,000 subscribers, actual capacity depends on the hardware configuration.

Maximum number of managed components supported by BMP

BMP can manage maximum 800 components (CBP or OCG), while actual number of managed

components depend on the capacity of BMP.


Performance of Provisioning

For each BMP Application configured with ATAE (R2+), the performance of provisioning can reach 50

CAPS. For totally 3 BMP Applications with 3 pair BMP DB, the performance of provisioning is about

100CAPS~150CAPS in off-peak time.

Above performance data is for reference. The actual provisioning performance for RAX OCS project

should be according to the real testing result in RAX project environment.

Performance of Web Service protocol

Below is web service command performance test result in ATAE R2 platform:

Business

Transaction

TPS CAPS Average

Response

Time

(seconds)

CPU(BMP)

IDLE

CPU(CBP)IDLE

Integration Inquiry 338.96 54.41 0.85 7.79 95.96

Balance Inquiry 138.07 135.27 0.22 6.62 93.18

Voucher Recharge 126.81 86.40 0.58 45.22 92.88

Adjustment 136.43 134.00 0.21 8.59 90.29

Create a subscriber 547.35 34.95 0.86 4.35 97.06

First Activation 305.97 61.00 0.49 6.68 82.12

Subscribe a product 472.23 41.11 0.95 2.94 94.73

Create a subscriber in

batch mode

342.17 24.90 <3.5 57.4 97.18


USAU


From the above figure, you can see that USAU not only can access narrowband SS7 network but

also can access broadband SIGTRAN signaling via IP package switched network

SS7

The SS7signaling system of USAU can provide MTP - message transmission part, SCCP - signaling

connection control part and TCAP - Transaction Capabilities Application Part. The position of these

function modules in system is shown below:

Distribution of Narrowband Signaling Function Modules in USAU

SIGTRAN

In this proposed CBS project , Aims at RAX’s full IP plan ,SIGTRAN will be deployed .

SIGTRAN is the signaling system of USAU, which can provide SCTP (Stream Control Transmission

Protocol), M3UA (MTP3 User Adaptation Layer) and so on. The distribution of these modules is listed

below:

Distribution of Broadband Signaling Function Modules in USAU


The transmission path of TDM –carried SS7 is shown below:

The path of TDM-carried SS7

E1 interface of EPI provides TDM PCM interface to access standard 64K link or 2M link.

EPI processes message of MTP1, extracts signaling slot and sends it to WCSU board via internal HW.

WCSU board processes message of MTP2 layer, MTP3 layer and above layers.

The path of IP signaling/protocol in USAU is shown below:

The path of IP signaling/protocol in USAU

The path of IP signaling/ protocol in traffic module is presented below:

BFII board receives message of IP signaling/protocol and send it to IFM board via fixed connection.

EPII WCSU

HWE1

EPII WCSU

HWE1


IFM processed message of MAC layer then distributes it to the specified BSG board according to IP

address and port number. This is the layer 1 message distribution.

BSG performs layer 2 distribution (high-level distribution), which will distribute message to WCCU via

Ethernet bus. The second traffic from BSG to WCCU distributes SCCP message. At that time, BSG

terminates SIGTRAN message.

WCCU processes user message of MTP3 layer and the MTP3 above layers.

Fig:: Position of USAU in the OCS Network


Each OCG Capacity: 3700k, totally support: 3700k*3 = 11100k (subs)

Each CBP Capacity: 2400K, totally support: 2400k*5= 12000k (subs)

Site 3 (DR, 14.4M):

Each OCG Capacity: 3700k, totally support: 3700k*4 = 14800k (subs)

Each CBP Capacity: 2400K, totally support: 2400k*6 = 14400k (subs)


SUMMARY:::

ATM

Automatic Teller Machine

APRU Average Revenue Per User

BMP Business Management Point

BSS/OSS Business and Operation Support System

BHCA Busy Hour Call Attempt(s)

CAPS Call Attempts Per Second

CC Customer Care

CDR Charging Data Record

CRBT Colorful Ring Back Tone

CRM Customer Relationship Manager

CP Content Provider

CoS Class of Subscriber

DCC Diameter Credit Control

FNS Familiarity Number Service

GPRS General Packet Radio Service

MML Man Machine Language

MMS Multimedia Messaging Services

NE Network Element

OCS Online Charging System


PCS Pieces

OCG Open Charging Gateway

SMS Short message Service

SP Service Provider

SOAP Simple Object Access Protocol

USSD Unstructured Supplementary Service Data

HUAWEI One Brand of Huawei

END of the Summary of Convergent Billing System Concept; Based on Huawei CBS

104215649 lecture cbs of huawei july2012(1)

Documents