01-01 System Description
01-01 System Description
01-01 System Description
Contents
1 System Description....................................................................................................................1-1
1.1 Product Introduction.......................................................................................................................................1-2
1.1.1 Product Features....................................................................................................................................1-2
1.1.2 Service Functions..................................................................................................................................1-3
1.1.3 Operation and Maintenance Function...................................................................................................1-3
1.2 Hardware Structure.........................................................................................................................................1-4
1.3 Software Architecture.....................................................................................................................................1-7
1.3.1 Key Terminologies................................................................................................................................1-7
1.3.2 Overall Architecture: overall architecture.............................................................................................1-8
1.3.3 Service Processes..................................................................................................................................1-9
1.4 Functional Principles....................................................................................................................................1-11
1.4.1 Key Terminologies..............................................................................................................................1-11
1.4.2 Communication Between Dual Systems.............................................................................................1-11
1.4.3 Communication with MSOFTX3000..................................................................................................1-11
1.4.4 Communication with the Billing Center.............................................................................................1-13
1.4.5 Communication with the NMS and client...........................................................................................1-13
1.5 Main Technical Parameters...........................................................................................................................1-14
1.5.1 System Specifications.........................................................................................................................1-14
1.5.2 Environment Specifications................................................................................................................1-14
1.5.3 Reliability Specifications....................................................................................................................1-15
Figures
Figure 1-3 Location and application of the iGWB network adapter (at the back of the IBM server chassis)....1-6
Figure 1-4 Location and application of the iGWB network adapter (at the back of the DELL 2950 server
chassis).................................................................................................................................................................1-6
Tables
1 System Description
Title Description
1.1 Product Introduction Introduces the features and functions of the iGWB.
1.2 Hardware Structure Introduces the hardware devices of the iGWB.
1.3 Software Architecture Introduces the software architecture of the iGWB.
1.4 Functional Principles Introduces how the iGWB communicates with other
devices and how it processes CDRs.
1.5 Main Technical Parameters Introduces the technical parameters of the iGWB.
LAN: Local Area Network WAN: Wide Area Network NMS: Network Management System
The iGWB is a large-capacity billing gateway developed by Huawei. With advanced software
and hardware techniques, the iGWB provides powerful CDR storage and conversion
capabilities and supports the interconnection with a billing center through File Transfer
Protocol (FTP) or File Transfer Access Management (FTAM) protocol.
High Reliability
Dual-system
Because of the special position of the billing system in networking, high reliability of the
iGWB is demanded. To achieve that, the iGWB adopts a dual-system design in both hardware
and software. In addition, the iGWB provides an automatic switchover protection mechanism
between the dual systems to ensure the operation reliability and service continuity.
Data Redundant Backup
The iGWB adopts RAID5 plus hot spare. The purpose is to ensure that data will not be lost in
the event of a fault occurring to one of the hard disks.
Network Backup
The iGWB can automatically back up CDR files to another storage devices through WAN or
LAN, to further improve the data security.
Auto-control
The iGWB can automatically boot up through the monitor module in case of a power failure.
The purpose is to ensure the normal running of the system when unattended.
Multi-Access
The iGWB can receive and process CDRs in various formats simultaneously, store them in the
channel of the backsave folder separately, and provide them to the billing center.
Large Capacity
The hard disks configured in the iGWB provide a sufficient valid capacity to store the CDRs
that are generated by the MSOFTX3000 in at least seven days in the case of maximum
subscriber quantity. In addition, the iGWB is scalable in hard disk capacity.
iGWB Server
The iGWB server is the core device of the iGWB system and adopts a dual-system design.
Currently, you can use the following servers:
Two IBM x3650T servers
Or two DELL 2950 servers
Each server provides four network adapters: two for communication with the MSOFTX3000,
one for the billing center, and one for the NMS.
Because the servers are updated periodically, the server type may be different the delivered one. Please
refer to the delivered one.
When the IBM x3650 server is used, the location and application of the network adapter
in the iGWB server is shown in Figure 1-3.
Figure 1.1 Location and application of the iGWB network adapter (at the back of the IBM server
chassis)
To BC (#3 Network
To #1 LAN Switch interface)
(#2 Network interface)
When the DELL 2950 server is used, the location and application of the network adapter
in the iGWB server is shown in Figure 1-4.
Figure 1.2 Location and application of the iGWB network adapter (at the back of the DELL 2950
server chassis)
For the convenient of description, the four network adapters are numbered as shown in
Table 1-1.
No. ID Function
KVMS
The active iGWB, the standby iGWB, and a Back Administration Module (BAM) are
configured in the integrated configuration cabinet. An KVMS is thus configured in the
cabinet, used to achieve operation control and switch of input and output devices, such as
liquid crystal display (LCD), keyboard, and mouse.
LAN Switch
LAN Switch is the communication channel between the iGWB and the MSOFTX3000.
Generally, Huawei’s Quidway series products are selected for this purpose. Two LAN
Switches are configured in the integrated configuration cabinet.
Power Supply
The power distribution box in the integrated management cabinet supplies power for the
iGWB. The nominal voltage is –48 V DC.
Client
The iCG9815 uses the concepts of server and client. Typically, you need to install a PC where
the iCG9815 Client resides in the equipment room. This PC works as a local client. You also
need to install such a PC in the NMS center as the remote client.
Access Point
To access two or more same or different switches, “access point” is used in the design of the
iGWB. Based on the parameter configuration and operation maintenance, one access point is
associated with one ap_proc process. This process realizes the modules that communicate
with the switches and the modules that store and transform the CDRs.
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.
The original CDRs are generally stored in d:\frontsave in the iGWB server. This path is called
the frontsave folder.
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.
The final CDRs are generally stored in e:\backsave in the iGWB server. This path is called the
backsave folder.
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, but not
hard-coded.
Active/Standby
Active/standby is a pair of basic concepts for a cluster system. In a cluster system, if a node
provides external services, its state is called “active”. If a node currently does not provide
external services, its state is called “standby”.
Primary/Secondary
Primary/Secondary is a basic concept for a cluster system. In a cluster system, two nodes may
be peered or not peered. If they are not peered, then they can be defined as primary or
secondary. In this case, one node will be set with highest priority. If this node runs normally, it
has the priority to control the resources of the cluster system.
Resources
The physical equipment and logical equipment that are shared by the nodes of the cluster
system are called “resources”, such as shared storage media, and virtual IP address.
entire software forms a multi-process and multi-thread architecture. For the communication
modes between processes, the iGWB adopts the client/server mode (currently, this is the most
mature application mode). Specially, the iGWB has one process as the core process with other
processes as sub-processes so that one process can schedule and monitor the sub-processes of
other services.
The overall software architecture of the iGWB is shown in Figure 1-5.
Dual-system
process
Parameter
Configuration
iGWB Server Process
Frontsave Module
Bill Center
Virtual IP Address
The virtual IP address keeps the connection between the iGWB dual systems and the
MSOFTX3000 and the iGWB operation and maintenance system in case of the switchover of
the dual systems. The virtual IP address of the iGWB is configured through the igwb.ini file.
If you use the single system, you do not need to configure the virtual IP address, and the IP
address of the network adapter is enough.
FE FE To BC
Frame 0
FE iGWB0
To BC
3×FE
0# LAN Switch
Frame 1
To NM S
Frame 9
LMT LMT LMT
MSOFTX3000
FE: Fast (100 Mb) Ethernet Interface LAN Switch: Local Ethernet switch
LMT: Local maintenance terminal -
The following introduces the flow of sending CDRs by the MSOFTX3000 from three phases:
In the MSOFTX3000 host
The flow of transferring CDRs is triggered by the internal timer of the MSOFTX3000.
The MSOFTX3000 monitors the bill pool. If there is a CDR in the bill pool, the
MSOFTX3000 sends it to the iGWB immediately. The timer is set to millisecond, so the
CDRs are sent in real time.
To transfer the CDRs normally, active channel and emergency channel are designed in
the MSOFTX3000 host. There are two channels for CDR transfer between the Calling
Control Unit (CCU) and the iGWB in each frame.
− Active channel: The CCU sends CDRs to the core LAN Switch directly through the
System Management Unit (SMU).
− Emergency channel: When an error occurs to the TCP connection between the SMUI
and the iGWB, the CCU selects a channel from the frame where it locates to a normal
frame, and sends CDRs to the SMUI of the normal frame. The SMUI of the normal
frame then sends the CDRs to the core LAN Switch.
In the core LAN Switch
Two LAN Switches forms the active and standby planes of the core LAN Switch.
− The 0# core LAN Switch sends CDR files to network adapter 1 of the active and
standby iGWB servers, to form the active plane CDR transfer channel.
− The 1# core LAN Switch sends CDR files to network adapter 2 of the active and
standby iGWB servers, to form the Standby plane CDR transfer channel, which also
serves as the first heartbeat path of the two servers.
− Two core LAN Switch communicates with each through cascade cables.
Between the dual systems
− Network adapter 1 of the active and standby iGWB servers receives CDRs from the
active plane CDR transfer channel through a virtual IP address.
− Network adapter 2 of the active and standby iGWB servers receives CDRs from the
standby plane CDR transfer channel through a virtual IP address.
DELL Server