Professional Documents
Culture Documents
Contents
1 Product Overview.......................................................................................................................1-1
1.1 Product Orientation.........................................................................................................................................1-2
1.2 Typical Networking.........................................................................................................................................1-2
1.3 Networking Interfaces.....................................................................................................................................1-2
2 Product Features.........................................................................................................................2-1
2.1 Flexible CDR Processing................................................................................................................................2-2
2.2 Large Capacity and Powerful Processing Performance..................................................................................2-2
2.3 Scalability........................................................................................................................................................2-2
2.4 High Reliability...............................................................................................................................................2-2
3 Product Functions.......................................................................................................................3-1
3.1 Service Functions............................................................................................................................................3-2
3.1.1 CDR Processing Functions.....................................................................................................................3-2
3.1.2 Charging Interface Functions.................................................................................................................3-3
3.1.3 Backing Up CDR Files Through a Network..........................................................................................3-3
3.2 Operation and Maintenance Functions............................................................................................................3-3
3.2.1 Browsing and Querying CDRs...............................................................................................................3-4
3.2.2 CDR Management Functions.................................................................................................................3-4
3.2.3 Security Management Functions............................................................................................................3-4
3.2.4 Configuration Management Functions...................................................................................................3-5
3.2.5 Performance Management Functions.....................................................................................................3-5
3.2.6 Fault Management Functions.................................................................................................................3-5
4 Product Structure........................................................................................................................4-1
4.1 Hardware Structure.........................................................................................................................................4-2
4.1.1 Rack........................................................................................................................................................4-2
4.1.2 iGWB Server..........................................................................................................................................4-4
4.1.3 KVMS....................................................................................................................................................4-6
4.1.4 LAN Switch............................................................................................................................................4-6
4.1.5 Power Distribution Box..........................................................................................................................4-6
4.1.6 Maintenance Terminal............................................................................................................................4-6
4.2 Software Structure...........................................................................................................................................4-7
4.2.1 Kernel Process........................................................................................................................................4-8
4.2.2 Access Point Process..............................................................................................................................4-8
6 Reliability....................................................................................................................................6-1
6.1 Hardware Reliability.......................................................................................................................................6-2
6.2 Software Reliability.........................................................................................................................................6-2
6.3 CDR Reliability...............................................................................................................................................6-3
6.3.1 CDR Receiving......................................................................................................................................6-4
6.3.2 CDR Processing Reliability...................................................................................................................6-5
6.3.3 CDR Backup..........................................................................................................................................6-5
7 Technical Specifications...........................................................................................................7-1
7.1 Performance Specifications.............................................................................................................................7-2
7.2 Reliability Specifications................................................................................................................................7-2
7.3 Operating Environment Requirements............................................................................................................7-3
Figures
Tables
1 Product Overview
This topic describes the definition and typical networking of the iGWB, and the standards that
the iGWB complies with.
1.1 Product Orientation
This topic describes the definition of the iGWB.
1.2 Typical Networking
This topic describes the typical networking of the iGWB and the protocols used by the iGWB.
1.3 Networking Interfaces
This topic describes the internal and external networking interfaces of the iGWB.
The iGWB is a large-capacity charging gateway developed by Huawei. Located between NEs
and the BS, the iGWB receives and stores the CDRs generated by the NEs, converts the format
of the CDRs to generate final CDRs required by the BS, and then sends the final CDRs to the
BS.
External Interfaces
iGWB-BS Bi FTP/FTAM/SFTP
Internal Interfaces
2 Product Features
This topic describes the features of the iGWB, including flexible CDR processing, excellent
performance, and scalability.
2.1 Flexible CDR Processing
The iGWB provides various functions of processing CDRs to meet carriers' requirements on
CDR formats. These functions involve receiving and buffering CDR files, converting the format
of CDRs, and sorting CDRs.
2.2 Large Capacity and Powerful Processing Performance
The iGWB provides the function of processing CDRs with excellent performance and the
function of storing CDRs with large capacity.
2.3 Scalability
This topic describes the scalability feature of the iGWB. This feature helps to expand services
effectively.
2.4 High Reliability
This topic describes high reliability of the iGWB.
In general, the BS of a carrier has special requirements on the format of CDRs. For example, a
carrier requires to extract some specific fields from original CDRs to form new CDRs and then
provide the new CDRs for the BS. To meet the requirements on various CDR formats, the
iGWB provides the function of configuring and converting the format of CDRs flexibly. The
functions of processing CDRs are described as follows:
l Receiving and buffering CDR files
l Sorting CDRs
l Converting the format of CDRs
The iGWB uses the disks with large capacity and processors with excellent performance, so it
provides large CDR storage capacity and powerful CDR processing performance. In standard
configuration, the iGWB can ensure that:
l Each pair of servers can process 3000 CDRs per second.
l Original CDR files and final CDR files can be stored for at least seven days.
2.3 Scalability
This topic describes the scalability feature of the iGWB. This feature helps to expand services
effectively.
l The iGWB employs the modular design. You can add new modules to introduce new
functions and new technologies, thus extending the application scope. This helps to expand
the capacity and upgrade the functions.
l To meet the requirement on large system capacity, you can improve the service support
capability of the iGWB by upgrading or adding disks.
The iGWB uses the following mechanisms to ensure high reliability of the system:
l All the key devices and components of the iGWB are redundant in 1+1 backup mode. These
components include servers, power modules, and Ethernet ports.
l The local disk of the server uses RAID1 or RAID5+Hotspare error tolerance technology
to ensure the safety of the system files and CDR files.
l The iGWB sends CDR files in real time to the storage device for backup. This ensures the
security of the CDR files.
l The iGWB can automatically restore damaged status files. This improves the reliability of
file backup and system recovery effectively.
l Multiple physical charging links can be set up between the iGWB and the SOFTX3000.
When a charging link fails, the charging services on the link are automatically switched
over to another available charging link.
For details on the reliability of the iGWB, see 6 Reliability.
3 Product Functions
This topic describes the powerful functions of the iGWB in terms of services and operation and
maintenance.
3.1 Service Functions
This topic describes the CDR processing functions, charging interface functions, and the function
of backing up CDRs through a network.
3.2 Operation and Maintenance Functions
The iGWB supports the human machine interface for providing operation and maintenance
functions. The functions involve CDR management, security management, configuration
management, fault management, and performance management.
The iGWB uses the customized Sliding Window Protocol to receive the CDRs generated by the
SOFTX3000 in real time. This prevents repetition or loss of CDRs.
Sorting CDRs
The iGWB stores final CDRs in different channels based on specific sorting conditions. You
can configure the rules for sorting final CDRs as required. For example, the iGWB can sort final
CDRs by CDR type and then store them by type in different directories. The CDR sorting
function of the iGWB meets the requirements for the BS on different charging strategies and
helps the BS to process CDR files.
Storing CDRs
l Storing original CDR files
The iGWB stores the received or collected original CDRs on the disks as original CDR
files with a fixed size.
l Storing final CDRs
The iGWB processes original CDRs, generates final CDRs, and stores the final CDRs on
the disks as final CDR files.
The iGWB can delete original CDRs and final CDRs automatically.
The original CDRs and final CDRs are stored as CDR files. You can set storage time for them.
Once the time for storing the original CDRs and final CDRs exceeds the preset value, the
iGWB deletes these files automatically.
The iGWB uses flexible charging interfaces. The charging interfaces provide the following
functions:
l Supporting the FTP ,SFTP and FTAM protocols between the iGWB and the BS
l Supporting the configuration of CDR file names, file size, and file generation duration
l Supporting flexible conversion between CDR formats
The iGWB can back up CDR files in real time to the storage devices on other computers on a
network. This improves data security.
By monitoring the performance of the iGWB, you can know the current running status of the
iGWB. This helps you to find and identify problems.
3.2.6 Fault Management Functions
The iGWB provides excellent fault management functions, including alarm management and
maintenance management.
Permission Management
The users of the iGWB are classified into four types with different permissions:
l Admin:
The users at this level have all the permissions. The permissions include operator
management, log browse, CDR browse and query, system maintenance, manual
switchover, file management, and masked alarms management.
l Operate:
By default, the users at this level have the permissions, such as log browse, CDR browse
and query, system maintenance, manual switchover, file management, and masked
alarms management.
l Normal:
By default, the users at this level have the log browse and CDR browse and query
permissions.
l Third:
By default, the users at this level have the log browse and CDR browse and query
permissions. The users that have the operator management permission can change the
permissions of the users at this level.
User Management
The iGWB provides the functions of querying, adding, modifying, and deleting users.
Log Management
Logs record the information about the operations performed by users on the device and the
running status of the device The iGWB provides the functions of browsing and querying logs.
You can query the operation logs of a specific user at a specific time or system logs.
By querying and monitoring logs, you can find illegal operations and the causes of system faults.
Then you can take proper measures to ensure network security.
Alarm management means finding and submitting the information about system errors and
exceptions to the NMS in real time. Multiple alarms are reported, such as the alarms on
insufficient medium space, file read-write errors, switchover, failure for the BS to obtain
CDRs for a long time, and heartbeat interruption.
l Maintenance management
The iGWB Client provides a friendly GUI to facilitate maintenance.
l Switchover upon a fault
The iGWB uses two servers to form a two-node cluster system in 1+1 backup mode. The
service processes of the iGWB run on only one server at a time. When one server is faulty,
the other server immediately takes over the applications on the faulty server through
software diagnosis (heartbeat diagnosis). In this way, the system can provide services
continuously without human intervention. This improves system reliability.
4 Product Structure
This topic describes the hardware and software structures of the iGWB.
4.1 Hardware Structure
This topic describes the hardware structure of the iGWB and the locations of the components in
the rack.
4.2 Software Structure
This topic describes the software structure and service processes of the iGWB.
4.3 Software and Hardware Configuration
This topic describes the configuration required for normal running of the iGWB, including
software and hardware configuration on the server and client.
4.1.1 Rack
This topic describes the rack where the iGWB is located.
In the SOFTX3000, the service shelves of the iGWB and SOFTX3000 are installed in the same
rack. The iGWB uses the N68E-22 rack developed by Huawei.
Figure 4-1 shows the N68E-22 rack.
The 19-inch N68E-22 rack complies with the following international standards:
l IEC60297-1, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
1:Panels and racks
l IEC60297-2, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
2:Cabinets and pitches of rack structures
l IEC60297-3, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
3:Subracks and associated plug-in units
In the SOFTX3000, the iGWB and the SOFTX3000 basic service processing frame are
configured in the same cabinet (integrated configuration cabinet). The related hardware
components include active and standby iGWB servers, core LAN Switches, and a keyboard,
video and mouse switch (KVMS), as shown in Figure 4-3.
Expansion subrack(01)(9U)
Air deflector(2U)
Basic subrack(00)(9U)
Air deflector(2U)
KVMS(1U)
LANSwitch(1U)
Cabling trough(1U)
LANSwitch(1U)
Cabling trough(1U)
Dummy panel(3U)
Dummy panel(1U)
BAM(2U)
Dummy panel(1U)
iGWB1(2U)
Dummy panel(1U)
iGWB0(2U)
Dummy panel(3U)
Dummy panel(2U)
The iGWB server is the core device of the iGWB system and adopts a dual-system design.
Currently, you can use the following servers:
l Two IBM x3650T servers
l Or two DELL 2950 servers
two for communication with the SOFTX3000, one for the billing center, and one for the NMS.
NOTE
Please refer to the delivered one.Because the servers are updated periodically, the type of the server may
be different from the one delivered. Please refer to the one delivered.
When the DELL 2950 server is used, the location and application of the network adapter in the
iGWB server is shown in Figure 4-4. For the convenience of description, the four network
adapters are numbered as shown in Table 4-1.
Figure 4-4 Figure 4-4 Location and application of the iGWB server network adapter(at the back
of the IBM server chassis)
Table 4-1 Table 4-1 Description to the iGWB server network adapters
NO Network adapter Description
When the IBM x3650 server is used, the location and application of the network adapter in the
iGWB server is shown in Figure 4-5. For the convenient of description, the four network
adapters are numbered as shown in Table 4-1.
Figure 4-5 Figure 4-5 Location and application of the iGWB network adapter(at the back of the
DELL 2950 server chassis)
4.1.3 KVMS
This topic describes the functions of the keyboard, video, and mouse switch (KVMS).
The rack holds three servers, including the primary and secondary iGWB servers, and BAM.
Therefore, a KVMS is configured in the rack for switching input and output devices such as the
LCD, keyboard, and mouse to control operations.
LAN switches are communication channels between the iGWB and the SOFTX3000. In general,
Quidway series products are used. The rack is equipped with two LAN switches during delivery.
The iGWB is powered by the PDB of the rack. In addition, the nominal voltage is -48 V DC.
The iGWB provides the device maintenance and management Client based on GUI and MML.
Through the Client, you can perform local and remote maintenance tasks, including
configuration management, service maintenance, performance statistics, service tracing,
security management, fault management, alarm management, and environment and power
supply monitoring.
The iGWB is a client/server model. Typically, you need to install a PC installed with the
iGWB Client in the equipment room. This PC works as a local maintenance terminal (LMT). In
addition, you need to install another PC installed with the iGWB Client in the NMC. This PC
works as a remote maintenance terminal.
Cluster
process
Parameter
configuration
iGWB server
process
Data flow
Control flow
As shown in Figure 4-6, the iGWB Server consists of the kernel process, access point process,
operation and maintenance process, cluster process, and parameter configuration process. Each
process contains various independent service thread modules.
Except the parameter configuration process, each process contains a management module and
a message relay module.
l Management module
Used to manage and dispatch the modules in the process.
l Message relay module
Used to forward messages between the processes and in the process.
4.2.1 Kernel Process
This topic describes the functions of the kernel process and the relations between the kernel
process and other processes.
4.2.2 Access Point Process
This topic describes the functions and modules of the access point process.
As the core of the iGWB software, the kernel process is the TCP/IP server of the access point
process, O&M process, and cluster process. It starts, stops, and monitors the ACM process,
access point process, and O&M process. The kernel process consists of a message relay module,
a management module, a cluster monitoring module, and a cluster interface module.
The access point process integrates the key service functions of the iGWB. The functions involve
CDR receiving, CDR processing, and CDR storage. The modules performing these service
functions are the network module, frontsave module, CDR process module, and backsave
module. These four modules form a unidirectional CDR processing process, as shown in Figure
4-7.
Format engine
Original
CDR E:\
D:\ E:\
backsave
frontsave backsave
\Second
It uses the customized Sliding Window Protocol to receive original CDRs to avoid
repetition or loss of CDRs.
l Frontsave module
It stores the CDRs that are received by the nework module.
l CDR processing module
It sorts CDRs, converts the format of CDRs, and generates and sends final CDRs to the
backsave module.
l Backsave module
It stores final CDRs in different channels, generates final CDR files, and provides them for
the BS.
The cluster process is used to start and manage the kernel process, thus managing the two-node
system.
The parameter configuration process is the parameter configuration module of the iGWB. The
iGWB provides the function of configuring parameters remotely through the GUI of the
Parameter Config Console.
The operation and maintenance process integrates the operatability and maintainability functions
of the iGWB. According to the functions, these service modules are classified into the log
module, backup module, CDR browsing and querying module, MML server module,
performance module, and alarm module. The modules are relatively independent from each
other.
Server
Table 4-2, Table 4-3, and Table 4-4 list the hardware configuration of the iGWB server.
NOTE
l Because servers are upgraded frequently, the hardware of iGWB servers may vary according to actual
situations. In this case, refer to the packing list.
l The iGWB uses two servers configured with the same hardware. One functions as the primary
iGWB server. The other functions as the secondary iGWB server.
When the iGWB server uses the DELL 2950, the hardware configuration of the DELL 2950 is
as shown in Table 4-2.
Item Configuration
Hard disk Five 146 GB hard disks configured as RAID 5+hot spare
When the iGWB server uses the IBM x3650T, the hardware configuration of the IBM x3650T
is as shown in Table 4-3.
Item Configuration
When the iGWB server uses the IBM x3650, the hardware configuration of the IBM x3650 is
as shown in Table 4-4.
Hardware Configuration
Hardware Configuration
Hard disk Five 146 GB hard disks configured as RAID 5+hot spare
Client
Item Configuration
Server
NOTE
The primary and secondary servers of the iGWB must be installed with the same software applications. Table
4-6 lists the required software applications. The software applications vary with servers. For a complete list,
refer to the packing list.
Windows 2000 Server OS Not required Used to install the OS and the
related protocol components.
FTAM and protocol stack Obtained from VERTERL To use the FTAM charging
installation software interface, install this software
(optional) application.
i3SAFE SIS SetWin2000 Obtained from Huawei Used to install the i3SAFE
(optional) SIS SetWin2000 anti-virus
software.
i3SAFE SIS SysPatron2000 Obtained from Huawei Used to install the i3SAFE
(optional) SIS SysPatron2000 anti-
virus software.
Client
This topic describes the principles for the iGWB to process CDRs. This helps you to be familiar
with the services of the iGWB.
5.1 CDR Processing Process
This topic describes the CDR processing process of the iGWB.
5.2 CDR Receiving Principle
This topic describes the principle for receiving CDRs, including the protocol used by the
iGWB and the interaction with other NEs.
5.3 CDR Processing Principles
This topic describes the principles for processing CDRs.
5.4 Principle for Storing CDRs
This topic describes the principle for storing CDRs.
5.5 Principle for Transmitting CDRs
This topic describes the principle for transmitting CDRs.
iGWB
CDR CDR CDR
receiving storage processing
Softswitch
BC
CDR CDR file CDR file
backup storage transmission
After the preprocessing, the final CDRs required by the BS are generated and sent to the backsave
module as a package for storage.
5.3.1 Encoding and Decoding
This topic describes the principles for encoding and decoding CDRs.
5.3.2 Sorting CDRs
This topic describes the principle for sorting CDRs.
5.3.3 Converting the Format of CDRs
This topic describes the principle for converting the format of CDRs.
No
No
Yes
Meet sorting Final
Channel n
condition n? CDRs
No
To meet the requirement of the BS, the SOFTX3000 needs to convert the format of the generated
CDRs.
The CDR processing module calls the format engine to convert the format of CDRs. Figure
5-3 shows the principle for converting the format of CDRs. Both an original CDR and a final
CDR are a set of fields. Therefore, converting the format of CDRs means converting the fields.
The fields in final CDRs are converted from the fields in original CDRs through different scripts.
Original
Field O1 Field O2 Field O3 Field O4 Field On
CDR
Final
Field F1 Field F2 Field F3 Field Fn
CDR
6 Reliability
This topic describes high reliability of the iGWB in terms of software and hardware.
6.1 Hardware Reliability
This topic describes the reliability of the iGWB hardware. The iGWB uses the two-node cluster
design and redundant hardware components to improve system reliability.
6.2 Software Reliability
This topic describes the reliability of the iGWB software. The iGWB uses the high availability
(HA) system, automatic fault detection mechanism, and backup mode to improve system
reliability.
6.3 CDR Reliability
This topic describes the mechanisms and methods that the iGWB uses to ensure CDR reliability.
Two-Node System
In the iGWB two-node system, each pair of servers work in active/backup mode. The automatic
switchover mechanism ensures system reliability and service continuity.
Local Disks
The iGWB adopts the most commonly used redundant array of inexpensive disks (RAID)
technology. It configures local disks with RAID1 or RAID5+Hot spare error redundancy
technology to prevent data from being lost during the breakdown of a disk.
Each server of the iGWB provides four network interfaces for communicating with the
SOFTX3000, BC, and NMS. This dual-plane structure improves system reliability.
Network Interfaces
Each server of the iGWB provides four network interfaces for communicating with the
SOFTX3000, BS, and NMS. This dual-plane structure improves system reliability.
l Both the primary server and the secondary server provide two network interfaces for
connecting to the SOFTX3000 to form a dual-plane network. The customized Sliding
Window Protocol ensures CDR transmission reliability.
l The primary server provides a network interface for connecting to the NMC, and the
secondary server provides a network interface for connecting to the LMT. This is isolated
from the network for receiving CDRs to ensure network security. The NE management
protocols include binary alarm protocols and MML specifications.
l Both the primary server and the secondary server provide a separate network interface for
connecting to the BS. In addition, the network interface is used to upload CDR files to the
BS through FTP, SFTP, or FTAM. This separate network interface ensures network
isolation and improves network security.
l On the external NM interface and charging interface, you can configure a firewall as
required. This prevents illegal attacks from the external network.
HA System
The two servers form an HA system in the parallel structure. This ensures stable running of the
system and meets the requirements on availability and reliability.
Data Security
l To protect important data, the iGWB provides automatic backup of charging data.
l System data is stored in different paths for redundancy backup. When an exception occurs,
system data is loaded and checked automatically.
Virtual IP Address
The virtual IP address technology is used to ensure normal connections between the
SOFTX3000 and the iGWB O&M system after the primary and secondary servers of the
iGWB are switched over.
Heartbeat Link
Heartbeat links are configured between the primary and secondary servers of the iGWB. The
heartbeat links are used to exchange handshake information between the primary and secondary
servers, know the running status of the peer server, and synchronize the status (such as the CDR
serial number and the status of the frontsave and backsave disks) of the two servers. This helps
to switch over the primary and secondary servers upon exceptions.
The system provides two heartbeat links (also called private networks):
l One heartbeat link is connected to the FABRIC2 network interface.
l The other heartbeat link is connected to the FABRIC1 network interface.
When one heartbeat link is disconnected, the iGWB servers use the other heartbeat link for
communications.
This topic describes how to ensure CDR reliability through CDR backup.
As shown in Figure 6-1, the iGWB receives CDRs from the SOFTX3000 through the LAN
switch by using the Sliding Window Protocol.
NOTE
Figure 6-1 takes a pair of servers as an example to describe the process of receiving CDRs.
FE FE
To the BC
0# shelf
FE
iGWB0
3×FE To the BC
0# LAN Switch
1# shelf
2# shelf
LAN Switch
To the NMC
9# shelf
l Primary channel
In normal cases, the SOFTX3000 directly sends CDRs to the LAN switch.
l Escape channel
When a failure occurs in the connection between a shelf of the SOFTX3000 and the
iGWB, the SOFTX3000 chooses a channel between it to any normal shelf through the
Ethernet and then sends the CDRs to the LAN switch through this channel.
The key data about the sliding window status in the iGWB is written into the hard disk in time.
When the iGWB is restarted or the primary and secondary servers are switched over, no CDR
is lost or duplicate during transmission.
Four modules are involved in the CDR processing process from receiving original CDRs to
generating final CDRs. The iGWB creates a reliable CDR processing task between the four
modules.
CDRs are processed in the unit of the package. After original CDRs are stored successfully, the
information about CDR packages is also stored in the hard disk. After original CDRs are
processed and stored as final CDRs, the package numbers are also stored. When the iGWB is
restarted, it can calculate the package number of the original CDRs that are not processed based
on the package numbers of final CDRs. Then the iGWB continues to process the remaining
original CDRs.
CDR backup further ensures CDR reliability. The iGWB automatically backs up CDR files on
other storage devices through the LAN or WAN to improve data security.
7 Technical Specifications
This topic describes the technical specifications required for normal running of the iGWB.
7.1 Performance Specifications
This topic describes the performance specifications of the iGWB server.
7.2 Reliability Specifications
This topic describes the reliability specifications of the iGWB.
7.3 Operating Environment Requirements
This topic describes the requirements on the operating environment of the iGWB.
A
ASN.1 Abstract Syntax Notation One
B
BAM back administration module
BER basic encoding rules
C
CCU calling control unit
CDR call detail record
D
DC direct current
F
FE Fast Ethernet
FTAM File Transfer Access Management Protocol
FTP File Transfer Protocol
G
GUI graphical user interface
HA high availability
I
iGWB iGateway Bill
IDE Integrated Device Electronics
IIS Internet Information Services
IP Internet Protocol
K
KVMS keyboard, video, and mouse switch
L
LAN local area network
LMT local maintenance terminal
M
MML human machine language
MTBF mean time between failures
MTTR mean time to repair
P
PC personal computer
PCI Peripheral Component Interconnect
R
RAID Redundant Arrays of Inexpensive Disks
S
SFTP Secure FTP
T
TCP Transfer Control Protocol
W
WAN wide area network
Index
E O
encoding and decoding, 5-3 operation and maintenance function, 3-3
operation and maintenance process, 4-9
F
P
fault management, 3-5
alarm management, 3-5 parameter configuration process, 4-9
maintenance management, 3-6 performance management, 3-5
switchover upon fault, 3-6 process
R
reliability
CDR, 6-3
hardware, 6-2
software, 6-2
S
security management function
log, 3-4
permission, 3-4
service function
backing up CDR file, 3-3
CDR processing, 3-2
charging interface, 3-3
SFTP, 1-2
software configuration
client, 4-12
server, 4-11
sorting CDR, 3-2, 5-3
storing CDR, 3-2
storing CDR principle, 5-5
T
technical specifications
operating environment requirements, 7-3
performance specification, 7-2
reliability specification, 7-2
transmitting CDR, 5-5
two-node system management, 3-5
typical networking, 1-2
U
user management, 3-5