13. igwb structure and principle issue 2.2

1www.huawei.com

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

iGWB Structure and

Principle

Page1Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Foreword

The CDRs generated by a switch are temporarily buffered in its

RAM that is generally known as the CDR pool. These CDRs must

be saved into physical media for CDR pools capacity limit and

volatile property.

Whats more, CDRs generated by the switch calls (generally

called the Original CDRs) can not meet the requirements of the

Billing System in terms of contents or format, thus, they have to be

pre-processed by the Charging Gateway (iGWB)

2Page2Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

References

HUAWEI iGWB User Manual


Objectives

Upon completion of this course, you will be able to:

Know the hardware structure of iGWB

Know the software structure of iGWB

Perform the parameter configuration for iGWB

Perform charging configuration


Contents

1. Overview

2. Hardware Structure

3. Software Structure

4. O&M


Contents

1. Overview



4. O&M


System Application

iGWB is Huawei standard charging gateway equipment, which locates

between the switch and the Billing System and is in charge of CDR

receiving, pre-processing and buffering.

Product PositionProduct Position

iGWB

Local operating console

TCP/IP FTP/FTAMWAN

MML MML M2000

Server

MSOFTX3000

Remote operating console

iGWB WAN

iGWB server

TCP/IP FTP/FTAMWAN

MML MML M2000

Charging system

MSOFTX3000Billing Center

iGWB

WAN

iGWB

Local operating console

TCP/IP FTP/FTAMWAN

MML MML M2000

Server

MSOFTX3000

Remote operating console

iGWB WAN

iGWB server

TCP/IP FTP/FTAMWAN

MML MML M2000

Charging system

MSOFTX3000Billing Center

iGWB

WAN


Product Functions

The main functions of iGWB in MSOFTX3000:

The iGWB receives CDRs from CCU/CSU in MSOFTX3000

through the sliding window protocol. It can prevent repeat and

missing.

Customize CDRs name, size and generation interval.

This is the basal function in charging interface of the iGWB.

We can configure CDRs name, size and generation interval.


Product Functions

Sorting CDRs and format conversion according to the operators

demands

Sorting CDRs :The iGWB can receive and process CDRs according to its

type. For example: CDRs are generated by LCS or and normal service.

The CDRs in different formats are stored separately and provided

respectively to the billing center.

Format Conversion: The charging system of carriers might have special

requirements for CDR format. For example, they might need the iGWB to

convert an original CDR in a binary format to a final CDR in another format

such as text format, Abstract Syntax Notation One (ASN.1) format and

abstract particular fields from an original CDR to generate a new CDR for

the billing center. The iGWB provides flexible CDR format configuration

and conversion functions to meet the diversified requirements of telecom

carriers.


Product Functions

Provide the opening directory to billing center.

Communicate with iGWB ,using FTPFile Transfer Protocol or FTAMFile TransferAccess & Management

If using FTPiGWB works as server ,billing system works as client

If using FTAMiGWB works as Responderbilling system works as initiator


Product Functions

Bill Processing Flow Of iGWB:

Note:

Arrowhead show the bill processing flow

The dashed between storage bills and backup bills shows that there is no

direct coupling in function

Switch Incept bills

Storage

original billsTransact bills

Storage

final billsBackup bills Billing center

iGateway Bill


Product Features

High reliability

Dual-plane

Automatic switchover mechanism upon fault to ensure reliability of the running

of the system and continuity of services

Hard disk sub-system adopting RAID mode

Software auto-startup and restart after exit

Auto-startup in case of power failure

Multi-access:

The iGWB can receive and process CDRs in different formats at the same time.

The iGWB stores these CDRs separately and provides them to billing center


Product Features

Flexible format conversion:

Provide flexible configuration and conversion of bill format.

Large capacity

CDRs can be stored in the iGWB at least seven days


Contents

1. Overview



4. O&M


Contents

2 Hardware Structure

2.1 Hardware Configuration

2.2 Principle


Hardware Configuration


Hardware Configuration

In the MSOFTX3000, the iGWB installed in integrated

configuration cabinet. The related hardware components

include

Active and standby iGWB servers

Disk array (except HP)

Core Local Area Network (LAN) Switches

An integrated converter


Hardware ConfigurationIBM iGWB Server: The iGWB Server communicates with MSOFTX3000 to

accomplish such operations as bill storage, format conversion and

preprocessing.

Disk Array: IBM EXP400 disk array are employed.

Integrated Shifter: The Keyboard/Video/Mouse (KVM) shifter is used to

implement switchover control of input/output devices. The integrated

shifter includes the input/output devices like Liquid Crystal Display (LCD),

keyboard, and mouse.

LANSWITCH: The LANSWITCH provides communication channel

between the iGWB and MSOFTX3000.

10


Hardware ConfigurationHP iGWB Server: HP ProLiant DL380 G3

Hard Disk: Its capacity is 5 hard disk(73.4GB) at most. Every server use

5 hard disk.

Integrated Shifter: The Keyboard/Video/Mouse (KVM) shifter is used to

implement switchover control of input/output devices. The integrated

shifter includes the input/output devices like Liquid Crystal Display (LCD),

keyboard, and mouse.

LANSWITCH : The LAN Switch is the communication channel between

the iGWB and MSOFTX3000.


Contents

2 Hardware Structure

2.1 Hardware Configuration

2.2 Principle

11


Connection Principle

Frame 0#

Frame 1#

Frame 2#

Frame 9#

LAN Switch in

plane 1

LAN Switch in plane 0

Standby iGWB

FE

FEActive iGWB

BAM

FE

Host Background

To the billing center

WS WS WS

HubTo the network

Management center

FE

To the billing center

Emergency WS



Network structure between iGWB and MSOFTX3000:

Active and standby iGWB servers communicate with the host

by the virtual IP. Only the active iGWB server can use the

virtual IP. That means MSOFTX3000 need not to care about

witch server is working.

The iGWB uses redundancy connections. There are four links

between iGWB servers and host.

SMU board will give a alarm when the network is broken

between the iGWB and MSOFTX3000.

12





The iGWB Server provides four network adapters to communicate

externally.

Local Area Connection 1 Connected to the NMS and the bill console.

Local Area Connection 2 Connected to LAN Switch0, communicating with

the active plane of host.

Local Area Connection 3 Connected to LAN Switch1, communicating with

the standby plane of host. Functioning as the first heartbeat path between the

active and standby iGWBs.

Local Area Connection 4 Connected to the billing center, providing billing

interface.

13



Heartbeat path

The system provides two heartbeat paths:

The first path uses Local Area Connection 3.

The second path uses serial port.


Summary

The iGWB hardware components include: active and standby

iGWB servers, disk array (except HP), core Local Area Network

(LAN) Switches, an integrated converter .

The iGWB uses the redundancy designing for backup.

14


Contents

1. Overview



4. O&M


Contents

3 Software Structure

3.1 iGWB processes

3.2 iGWB directory structure

15


Software StructureSoftware Structure

The iGWB is a client/server system with multi-processes and multi-

threads, The overall software architecture of the iGWB is shown in

graph below:

ap_proc.exe

knl_proc.exe

om_proc.exe

ap_proc.exe

. . . . . . cls_proc.exe

Exchange 1

Exchange N

. . . . . .

Bill console Bill console


Kernel Process

Kernel Process knl_proc.exe The kernel process is the core of the whole software. It acts as

the Transmission Control Protocol/Internet Protocol (TCP/IP)

server for the other processes. It is responsible for starting,

stopping, and monitoring the access point process and the

operation and maintenance process. This process is composed

of a message relay module, a management module, a dual-

system monitor module and a dual-system interface module.

16


Access Point Process

Access Point Process ap_proc.exe The access point process incorporates the main service

functions of the iGWB, including CDR receiving, CDR

processing, and CDR storage. The service functions are

integrated into a network module, a frontsave module, a CDR

processing module, and a backsave module.


Access Point Process

Bill processing flow

Receives bills and uses a particularprotocol to ensure bill transmission

against repetition or loss

Network module

Saves the bills received by networkmodule to form original bills

Front disk module

Combines and sorts bills as required,and transmits bills to back disk module

Bill processing module

Saves bills by channel to form final

bills and provides bills to billing center

Back disk module

FTP/FTAM Billingcenter

MSOFTX3000

Generates and

transmits bills

17


Contents

3 Software Structure

3.1 iGWB processes

3.2 iGWB directory structure


Software Directory

The structure of iGWB software installation directory :

c:\igwb

\ap_proc.exe

\cls_proc.exe

\knl_proc.exe

\om_proc(.exe)

\format.dll

\KillCluster.exe

\config\ini\iGWB.ini

\config\format/*

\trace

\config\specialformat

18


Basic Concept

Channel

Channel is a logical concept. A channel refers to the CDR processing

modes and storage directories that match a certain sorting condition.

Simply speaking, one channel is associated with one CDR storage

path.

Original CDR

The original CDRs refer to the unprocessed CDRs that the iGWB

receives from the switches. The original CDRs are saved in files with

a fixed size of 3MB for each in the iGWB disk. These files are called

original CDR files.


Basic Concept

Final CDR

The CDRs that have been preprocessed (sorting and format

conversion) by the iGWB are called final CDRs. The final CDRs can

be saved as fixed-size or fixed-interval files. These files are called

final CDRs.

Format Library

The format library is the core that the iGWB transforms the CDRs. It is

associated with one format conversion module (dynamic link library)

and a series of format configuration files. The format library is

designed to make the CDR format dynamically configurable.

19


Original bill saving directory :

d:\frontsave\X3KM

\20060101

. . .

\20060107

Original Bill Saving Directory


Final bill saving directory :e:\backsave

\X3KM\chl1

\20030101. . .

\20030107. . .\Second

\X3KM\chl1\chl2

Note:Each final CDR file can be save in one or two shares. If saved in two shares, the first one

has different directory structure with the second. 1. The first one is used to save and browse in local, and it will be delete by iGWB.2. The CDR files in second directory is shared with billing center and deleted by it. Otherwise, it will be deleted by iGWB.

Final Bill Saving Directory

20


Summary

Master the softwares process and functions

Know the software directory structure


Contents

1. Overview



4. O&M

21


Contents

4 O&M

4.1 Parameter Configuration

4.2 Basic Operations

4.3 MSOFTX3000 Related Configuration


Parameter Configuration On the parameter configuration console, you can modify and maintain the igwb.ini

configuration file, and you can compare the system parameters among different

offices. The parameter configuration console is a graphic user interface (GUI), as

shown in the following:

1

2

3

4

5

6

6. Menu bar 5.Toolbar4.Navigation tree

3. Status bar2.Sub-window1.Main window

22


Parameter Configuration

\config\ini\igwb.ini :[Common]

APCount = 1 ;Accesspoint count

ServerNo = 0 ;Server No., 0-Primary, 1-Secondary

NoCluster = 0 ;Flag of cluster or not, 0-cluster mode, 1-

single-host mode

[AccessPoint1]

APType = 4 ;Accesspoint type, 0-128, 1-MSC, 2-STP, 3-

GPRS, 4-WCDMA, 5-SOFTX

APName = X3KM ;Accesspoint name, need no modification

LocalIpToEx = 172.20.200.1 ;iGWB's IP to connect the mobile network

exchange

LocalPortToEx = 9901 ;iGWB's port bound with LocalIpToEx

LocalIpToExBak = 172.30.200.1 ;iGWB's secondary IP to connect the mobile

network exchange

LocalPortToExBak = 9901 ;iGWB's port bound with LocalIpToExBak



BillRecSize = 536 ;Original bill record size(Bytes)

SaveSecond = 1 ;Flag of offering the second copy of final bill

files, 0-no, 1-yes

BinAlarmSend = 1 ;Send binary alarm

BaseID = 3200 ;Binary alarm base ID

ProcBillCSN = 1

;BackSavePatchName = 3g_cs_asn1

[MML]

LocalIpToMMLClient = 10.77.240.9 ;iGWB's IP to connect client(VirtualIP of

Resource1)

[Cluster]

InstallShareDiskArray = 0 ;Flag of using sharing disk array, 0-no, 1-

yes

HeartBeatBroken = 300 ;Heartbeat link broken interval(seconds)

HeartBeatCount = 2 ;Heartbeat link count

ResourceCount = 3 ;Resource count

23



;Configuration of heartbeat link1

[Link1]

Type = UDP ;Heartbeat link type, UDP-private network,

COM-serial communication port

Name = UDP_LINK ;Heartbeat link name

LocalIP = 130.1.3.1 ;Local heartbeat IP(IP of local NIC1)

PeerIP = 130.1.3.2 ;Peer heartbeat IP(IP of peer NIC1)

;Configuration of heartbeat link2

[Link2]

Type = COM ;Heartbeat link type, UDP-private network,

COM-serial communication port

Name = COM_LINK ;Heartbeat link name

Port = 1 ;Port No., 1-COM1, 2-COM2


Parameter Configuration;Configuration of resource1

[Resource1]

ResType = IP ;resource type, IP-virtual IP

ResName = IP_OMC ;resource name, to connnect OMC or Client

OrginalIP = 130.1.1.1 ;original IP, IP of NIC1

VirtualIP = 10.77.240.9 ;virtual IP

VirtualMask = 255.255.255.240 ;subnet mask of virtual IP

;Configuration of resource2

[Resource2]

ResType = IP ;resource type, IP-virtual IP

ResName = IP_PLANE1 ;resource name

OrginalIP = 130.1.2.1 ;original IP, IP of NIC2

VirtualIP = 172.20.200.1 ;virtual IP

VirtualMask = 255.255.0.0 ;subnet mask of virtual IP

SwitchGroup = 1 ;Only all the resources in the same SwitchGroup

No. fail, the switch will be happened

;Configuration of resource3

24


Parameter Configuration;Configuration of bill

[DiskFile]

DeadLineOfAutoDel = 60

OrigFileMaxSize=3072

FinalFileMaxSize=4096

FinalFileMaxTime=600

;Configuration of backup parameters

[NetBackup]

UserName = anonymous ;FTP user name

DestHostIP = 130.1.3.2 ;Destination host IP address

LocalIP = 130.1.3.1 ;Local host IP address

Password=TsqNDv75BvLpHU

BeforeEncode=0

BackupTaskCount=1 ;Total number of backup tasks

;Configuration of BackupTask 1

[BackupTask1]

SourceDir = e:/backsave/X3KM/normal ;Source files' directory

DestDir = /back/X3KMBak ;Destination directory


Contents

4 O&M




25


Starting the iGWB

On the server, choose Start > Programs > iGateway Bill V200

Server > Start iGWB;

On your desktop, the icon is displayed in the status area of the

task bar. It indicates that the iGWB Server is properly started.

Note Starting precondition: The iGWB Server must be installed. And parameters are correctly configured in igwb.ini.

The iGWB Server must work well. Otherwise, the iGWB Client

cannot connect with it


Stopping the iGWB

Stop the Process Watch Dog (PWD) service on the active

server;

On the server, choose Start > Programs > iGateway Bill

V200 Server > Stop iGWB;

The bulb icon becomes gray and then disappears from the

status area. It indicates that the iGWB service is stopped. Note Stopping precondition: The iGWB Server must be installed. Stop the PWD service before you stop the iGWB Server.

If the PWD service is running, the iGWB Server process

automatically restarts again.

26


Logging In to the CDR Console The iGWB Server works well;

Choose Start > Programs > iGateway Bill V200 Client > iGWB Client, and then the

Login dialog box will be displayed.

Note Office IP address: The server connects with the client or the network management system (NMS) through the IP address.

The IP address must be consistent with the value of LocalIpToMMLClient

under MML in igwb.ini.


Resetting iGWB

It is used to reset the iGWB in client. You must be the super

operator or a user authorized to perform manual switchover. And

make sure to start the PWD service prior to the iGWB service;

On the CDR console, select Operation > Reset iGWB;

In the Warning dialog box, click Yes.

Note If the iGWB is reset, the CDR console is disconnected from the iGWB Server.

27


Managing CDRs

CDR management includes a series of important functions, including browsing,

querying, printing, saving CDRs and manually outputting CDR files;

Log in to the CDR console. The left pane shows the navigation tree that is divided

into several tab pages based on access points (for example, the X3KM node

shown in the following figure). The navigation tree displays the CDR storage mode

on the server.


Function Description

CDR management includes:

Browsing CDRs by Type

Browsing CDRs by Format

Browsing CDRs by Multiple Conditions

Saving CDR Information

Printing a CDR

Outputting a Final Bill Manually

28


Collecting CDR Statistics

CDR statistics is a major function provided by the iGWB. The user can set CDR

statistic condition to collect and analyze CDR statistics. You can collect statistics

on CDRs of multiple access points.

On the CDR console, select Operation > CDR Stat. to display the CDR Stat. dialog

box.


Collecting CDR Statistics

Data list

Pie diagramHistogram

You can select the style how the statistic result is

displayed:

29


Manual Switchover

To switch over the iGWB manually. You are the administrator or

an operator authorized to perform switchover;

On the CDR console, select Operation > Manual Switch;

In the confirmation prompt, click Yes. Check the bulbs at the

status area. Because the standby server is activated, its bulb

becomes on. Also, because the active server is deactivated, its

bulb becomes gray.

Note If the switchover is successful, the server is disconnected fromthe CDR console.


Contents

4 O&M




30


MSOFTX3000 Charging

Configuration Charging Tables in MSOFTX3000:

Home PLMN Roam Prefix table ADD HPLMNRP

Bill Processing Information TableADD BILLPROC

Long Bill Timer table SET LBTMR

Bill Control Information table ADD BILLCTRL

Modify General Bill Control Table MOD GBILLCTRL

DescriptionCommand


Summary

Know iGWB O&M

Perform charging configuration in MSOFTX3000 side.

31

Thank youwww.huawei.com

13. igwb structure and principle issue 2.2

Documents

huawei technologies

igwb structure

original cdrs

process cdrs

software structure of

hardware structure of

system application igwb

format conversion