Operator Logo

ZXUN CG Feature List

For IMS
V4.10
 ZXUN CG Feature List

ZXUN CG Feature List

Version Date Author Approved By Remarks

CN
V1.00 2011-04-20 Product Not open to the Third Party
Line

© 2022 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.

ZTE Confidential Proprietary © 2022 ZTE CORPORATION. All rights reserved. I

ZXUN CG Feature List

TABLE OF CONTENTS

1 Overview...........................................................................................................1

2 Basic Features.................................................................................................2
2.1 ZUF-06-01-005 Rf Interface...............................................................................2
2.1.1 Summary......................................................................................................2
2.1.2 Benefits........................................................................................................ 2
2.1.3 Description...................................................................................................3
2.2 ZUF-06-01-007 Collect ACRs from CSCF/MGCF/AGCF...................................4
2.2.1 Summary......................................................................................................4
2.2.2 Benefits........................................................................................................ 4
2.2.3 Description...................................................................................................4
2.3 ZUF-06-01-008 Collect ACRs from MMTel AS...................................................5
2.3.1 Summary......................................................................................................5
2.3.2 Benefits........................................................................................................ 5
2.3.3 Description...................................................................................................5
2.4 ZUF-06-02-001 CDR File Management.............................................................6
2.4.1 Summary......................................................................................................6
2.4.2 Benefits........................................................................................................ 6
2.4.3 Description...................................................................................................6
2.5 ZUF-06-02-002 CDR Code/Decode with ASN.1 Format (BER)..........................7
2.5.1 Summary......................................................................................................7
2.5.2 Benefits........................................................................................................ 7
2.5.3 Description...................................................................................................7
2.6 ZUF-06-02-003 CDR Filtering............................................................................8
2.6.1 Summary......................................................................................................8
2.6.2 Benefits........................................................................................................ 8
2.6.3 Description...................................................................................................8
2.7 ZUF-06-02-004 Configurable CDR File Creation...............................................9
2.7.1 Summary......................................................................................................9
2.7.2 Benefits........................................................................................................ 9
2.7.3 Description...................................................................................................9
2.8 ZUF-06-02-005 Bx Interface Supports FTP......................................................10
2.8.1 Summary....................................................................................................10
2.8.2 Benefits......................................................................................................10
2.8.3 Description.................................................................................................11
2.9 ZUF-06-03-001 O&M Functions.......................................................................11
2.9.1 Summary....................................................................................................11
2.9.2 Benefits......................................................................................................11
2.9.3 Description.................................................................................................12
2.10 ZUF-06-03-002 System Security......................................................................13
2.10.1 Summary....................................................................................................13
2.10.2 Benefits......................................................................................................14
2.10.3 Description.................................................................................................14
2.11 ZUF-06-03-003 SNTP Support........................................................................16
2.11.1 Summary....................................................................................................16

II ©2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

2.11.2 Benefits......................................................................................................16
2.11.3 Description.................................................................................................16

3 Optional Features..........................................................................................17
3.1 ZUF-06-04-001 CDR Query.............................................................................17
3.1.1 Summary....................................................................................................17
3.1.2 Benefits......................................................................................................17
3.1.3 Description.................................................................................................17
3.2 ZUF-06-04-004 CDR Routing..........................................................................17
3.2.1 Summary....................................................................................................18
3.2.2 Benefits......................................................................................................18
3.2.3 Description.................................................................................................18
3.3 ZUF-06-04-005 Customized CDR Format........................................................18
3.3.1 Summary....................................................................................................18
3.3.2 Benefits......................................................................................................18
3.3.3 Description.................................................................................................18
3.4 ZUF-06-04-006 Bx Interface Supports FTAM...................................................19
3.4.1 Summary....................................................................................................19
3.4.2 Benefits......................................................................................................20
3.4.3 Description.................................................................................................20
3.5 ZUF-06-04-007 Bx Interface Supports SFTP...................................................20
3.5.1 Summary....................................................................................................20
3.5.2 Benefits......................................................................................................20
3.5.3 Description.................................................................................................20
3.6 ZUF-06-04-008 CDR Merging for IMS Domain................................................21
3.6.1 Summary....................................................................................................21
3.6.2 Benefits......................................................................................................21
3.6.3 Description.................................................................................................22
3.7 ZUF-06-04-009 CDR Consolidation.................................................................22
3.7.1 Summary....................................................................................................22
3.7.2 Benefits......................................................................................................23
3.7.3 Description.................................................................................................23
3.8 ZUF-06-01-001 Ga Interface............................................................................23
3.8.1 Summary....................................................................................................23
3.8.2 Benefits......................................................................................................23
3.8.3 Description.................................................................................................24
3.9 ZUF-06-01-002 GTP’ Protocol Tracing............................................................25
3.9.1 Summary....................................................................................................25
3.9.2 Benefits......................................................................................................25
3.9.3 Description.................................................................................................25
3.10 ZUF-06-01-006 Diameter Protocol Tracing......................................................26
3.10.1 Summary....................................................................................................26
3.10.2 Benefits......................................................................................................26
3.10.3 Description.................................................................................................26

ZTE Confidential Proprietary © 2022 ZTE CORPORATION. All rights reserved. III
 ZXUN CG Feature List

FIGURES

Figure 2-1 Logical ubiquitous offline charging architecture.....................................................2

Figure 2-2 IMS domain offline charging architecture...............................................................4
Figure 3-1 Protocol Layer Relation between CDF and CGF Entities.....................................24
Figure 3-2 Interaction mode between modules in GTP’ signaling tracing system.................26
Figure 3-3 Interaction mode between modules in Diameter signaling tracing system...........27

TABLES

Table 2-1 Offline Charging Messages Reference Table.........................................................3

IV ©2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

ZTE Confidential Proprietary © 2022 ZTE CORPORATION. All rights reserved. V

 ZXUN CG Feature List

1 Overview
This document is about the features of ZXUN CG system.

Here clarify that the basic features are the basic functions for the elements running, and
optional features are enhanced functions due to some operator’s demands. The basic
and optional features can be adjusted according to the operator’s demands. That means
some basic features can be optional ones, while some optional features can be basic
ones, as a result of different requirements of operators.
 ZXUN CG Feature List

2 Basic Features

2.1 ZUF-06-01-005 Rf Interface

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.1.1 Summary
Rf is the reference points from the Charging Trigger Function (CTF) to the Charging
Data Function (CDF), and is intended for the transport of charging events. Rf is used for
offline charging. The following figures depict the position of the Rf reference points within
the overall 3GPP offline charging architecture.

Figure 2-1 Logical ubiquitous offline charging architecture

2.1.2 Benefits
Via Rf interface, CDF collects real time charging information generated by IMS NEs.

2 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

2.1.3 Description

For offline charging purposes between the CTF (Diameter client) and the CDF (Diameter
server) are carried out on the Diameter Rf reference point, where the CTF reports
charging information to the Charging Data Function (CDF).

Two basic scenarios are used:

 Event based Charging

 Session based Charging

The corresponding Diameter accounting application messages for the Charging Data
Transfer operation is Accounting Request (ACR) and Accounting Answer (ACA).

The following table describes the use of these messages for offline charging.

Table 2-1 Offline Charging Messages Reference Table

Command-Name Source Destination Abbreviation

Accounting-Request CTF CDF ACR
Accounting-Answer CDF CTF ACA

CTF can be configured multiple CDF with priority, when the connection towards the
primary CDF is broken, the process of sending accounting information is continued
towards a secondary CDF (if such a CDF is configured).

If no CDF is reachable, the network element buffers the generated accounting data in
non-volatile memory. Once the CDF connection works again, all accounting messages
stored in the buffer are sent to the CDF, in the order they were stored in the buffer.

In case a network element does not receive an ACA in response to an ACR, it may
retransmit the ACR message. The waiting time until a retransmission is sent, and the
maximum number of repetitions are both configurable by the operator. When the
maximum number of retransmissions is reached and still no ACA reply has been
received, the network element executes the CDF connection failure procedure as
specified above.

If retransmitted ACRs' are sent, they are marked with the T-flag as described in RFC
3588, in order to allow duplicate detection in the CDF, as specified in the next sub-
clause.

A Diameter client marks possible duplicate request messages (e.g. retransmission due
to the link fail over process) with the T-flag as described in RFC 3588.

If the CDF receives a message that is marked as retransmitted and this message was
already received, then it discards the duplicate message. However, if the original of the
re-transmitted message was not yet received, it is the information in the marked
 ZXUN CG Feature List

message that is taken into account when generating the CDR. The CDRs are marked if
information from duplicated message(s) is used.

The CDF closes a CDR when it detects that expected Diameter ACRs for a particular
session have not been received for a period of time.

2.2 ZUF-06-01-007 Collect ACRs from

CSCF/MGCF/AGCF
Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.2.1 Summary

CG collects ACRs from CSCF/MGCF/AGCF using Rf interface.

2.2.2 Benefits

CG supports collection of charging information from CSCF/MGCF/AGCF, When the

charging information has been processed in CG, it transfers the charging information to
billing systems, Collection and distribution of charging data either for charging or
accounting purposes are fundamental functions for an operator‘s revenue flow.

2.2.3 Description

Charging information in the IMS domain network is collected for each User by the
CSCF/MGCF/AGCF, which are serving that User. The CSCF collects charging
information for each UE related with the session and the Application Servers Involved,
while the MGCF collects charging information for each session related with the external
network, CSCF/MGCF/AGCF send the ACRs to the CDF using Rf interface, CDF
generate CDRs according to the ACRs, CG provide non-volatile CDR storage, and
transfer CDRs to the billing center using Bx interface.

Figure 2-2 IMS domain offline charging architecture

The CDRs include:

4 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

 S-CSCF-CDR: a CDR per session generated by S-CSCF

 P-CSCF-CDR: a CDR per session generated by P-CSCF

 I-CSCF-CDR: a CDR per session generated by I-CSCF

 MGCF-CDR: a CDR per session generated by MGCF

 AGCF-CDR: a CDR per session generated by AGCF

2.3 ZUF-06-01-008 Collect ACRs from MMTel AS

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.3.1 Summary
CG collects ACRs from MMTel AS using Rf interface.

2.3.2 Benefits
CG supports collection of charging information from MMTel AS. When the charging
information has been processed in CG, it transfers the charging information to billing
systems, Collection and distribution of charging data either for charging or accounting
purposes are fundamental functions for an operator‘s revenue flow.

2.3.3 Description
The MMTel charging encompasses the Multimedia telephony service together with the
associated supplementary services charging aspects, Multimedia telephony service and
supplementary services charging function focuses on charging information provided by
the CTFs supporting MMtel specific service charging: calling user identification, called
user identification, media component characteristics and usage (speech, video etc.),
supplementary services applied.

The MMTel offline charging functionality is based on the CTFs reporting accounting
information, by sending Diameter Accounting Requests (ACR) to the CDF, CDF
generate CDRs according to the ACRs, CG provide non-volatile CDR storage, and
transfer CDRs to the billing center using Bx interface as Figure 2 -2.

The CDRs includes:

AS-CDR: a CDR per session generated by MMTel AS.

 ZXUN CG Feature List

2.4 ZUF-06-02-001 CDR File Management

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.4.1 Summary
Provide the functions of CDR operation and maintenance to implement CDR file
management.

2.4.2 Benefits
The operator can use this feature freely and chose how to manage CDRs; all functions
are provided by the GUI based on Java.

2.4.3 Description
CDR operation and maintenance provide the following functions:

 Original ACRs Storage: ACRs, which are received from IMS NEs and are not
preprocessed by CG, are called original ACRs. CG can support original ACRs
storage. The original ACRs are stored in physical media for pre-defined or
configured days before they are deleted

 Original ACRs Auto-backup: CG can support original ACRs auto-backup. The

original ACRs can be kept to local disks for the ACR backup.

 Original ACRs Auto-deletion: CG can support original ACRs auto-deletion. The

original ACRs are stored in files, if the files are outdated, they will be deleted
automatically. Users can configure how many days the original ACRs files are
stored.

 CDRs Storage: CDRs preprocessed which will be transferred to the Billing System.
CG can support CDRs storage. The CDRs are stored in physical media for pre-
defined or configured days before they are deleted

 CDRs Auto-backup: CG can support CDRs auto-backup feature. Through the

appropriate configuration, it can back up to the local disk or remote backup through
the network. Remote backup refers to transfer the CDRs to a remote FTP server for
backup. Compression can be used to decrease the volume of data and thereby
reduce the amount of storage capacity needed for long-term storage, or to reduce
the file-transfer time in a network with low bandwidth.

6 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

 CDRs Auto-deletion: CG can support CDRs auto-deletion. The CDRs are stored in
files, if the files are outdated, they will be deleted automatically. Users can configure
how many days the final CDRs files are stored

 Instant File Update: Implement the generation of the manual intervention CDR,
enabling the operator to browse the arrived CDR contents in real time.

The CDR operation and maintenance module is divided into two software module: CDR
management process and client terminal. The client provides the UI so as to transmit the
user command to the server and display the executing result for user. The CDR
management processor in CG receives the messages from the client and achieves the
CDR file management.

2.5 ZUF-06-02-002 CDR Code/Decode with ASN.1

Format (BER)
Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.5.1 Summary

The coding format of the CDR data in the provided CDR file adopts ASN.1 BER format;

2.5.2 Benefits

Using the ASN.1 format, CG can easy to expand the CDR fields. CDR encoding with
ASN.1 (BER) can reduce the length of the CDR data.

2.5.3 Description

CG provides a set of CDR coding formats following to the 3GPP definition.

ASN.1 is a language that defines the way data is sent across dissimilar communication
systems. ASN.1 ensures that the data received is the same as the data transmitted by
providing a common syntax for specifying application layer protocols. ASN.1 is an
ISO/ITU-T standard based on the OSI model and is defined in “ASN.1 encoding rules:
Specification of Basic Notation, ITU-T Recommendation X.680”.

CGF uses ASN.1 Basic Encoding Rules (BER) to encode the CDRs. BER is a set of
standard rules, defined in “ASN.1 encoding rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) ITU-
T Recommendation X.690”. A field is encoded into the following parts:
 ZXUN CG Feature List

 Identifier: identifies the data type and ASN.1 tag.

 Length: the length of the content part in number of octets.

 Contents: the value encoded according to data type specific rules.

2.6 ZUF-06-02-003 CDR Filtering

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.6.1 Summary
As the front system of the Billing System, CG processes the collected CDR data as per
the special requirements of the operator and then provides the processed data to the
Billing System.

2.6.2 Benefits
CDR Filtering functions are used in order to control the data flow through CGF, so as to
reduce load in Billing Systems.

2.6.3 Description
CG screens the different interfaces between the different NEs and the Billing System to
achieve the collection of the CDR data and CDRs unification. Before the exporting of the
CDR data, CG conducts some special processing for the collected CDR, such as
merging, filtering etc.

The CDR Filtering functions provided by CG mainly include:

CDR Filtering: As the special requirements of the operator, remove some unnecessary
types of CDRs.

Field Filtering: As the special requirements of the operator, remove some unnecessary
fields.

The processed CDRs are sent to the Billing System.

8 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

2.7 ZUF-06-02-004 Configurable CDR File Creation

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.7.1 Summary
Generate the CDR files according to the parameters set in the configuration file.

2.7.2 Benefits
The parameters of the file generation include several conditions such as the file size and
the time interval. The configuration of the file size ensures the same file size; the
configuration of the time interval ensures the generation of the CDRs at the set time
point, enabling the CDR timely send to the Billing System and avoids the unnecessary
waiting time. These parameters can be modified through the configuration module in the
client terminal, after modifying, send it to CG and it will take effect immediately.

2.7.3 Description
The naming format of CDR files is: “A/B/C prefix + File name”.

The A/B/C prefix is a user-definable character, which is by default "A", "B" and "C",
usedto distinguish A, B and C files. The prefix keeps consistent in the entire CG.

A file name is specific to a channel, and can be defined differently for different channels.

The format of file name is also user-definable. A file name can contain letters and
numbers except ""/", ":", "*", "?", """, "<", "> and "|". Format characters, such as %Y, %M
and %D and so on, can be used in a file name so that the file name contains date and
time information, as shown in the following:

%Y The current 4-digit

%y 2-digit year
%M Month, 2 digits, fill 0 at the beginning to complete
%D Date, 2 digits, fill 0 at the beginning to complete
%h Hour, 2 digits, fill 0 at the beginning to complete
%m Minute, 2 digits, fill 0 at the beginning to complete
%C Channel ID, 2 digits, fill 0 at the beginning to complete
%N File sequence number, number of digits definable, fill 0 at the beginning

The format character %N is mandatory, while others are optional.

 ZXUN CG Feature List

The number of digits of file sequence number is also user-definable. If the file sequence
number is specified to be 5 digits long, then the file sequence number cycles between
00000 and 99999.

In addition, the file sequence number can be specified to start from 0 every day.When B
files are provided to the BD, the prefix B can be removed.

For example: A/B/C prefix is default, the file name string is defined as "zte_%Y%M%D_
%N.dat", and the sequence number is defined to be 5 digits long, then, the file bearing
the sequence number of 123 created on April 22, 2008 at 11:02 is named as:
zte_20080422_00123.dat.

The configuration of the file generation parameter stipulates the file generation reference
of CG. Several conditions may govern the closure of a CDR file by the CGF:

 A configurable file size limit;( value range: 2 ~ 65534kB)

 A configurable file lifetime ("interval"); (value range: 3~43200s)

These parameters need to be set at least one, and can be set both, any one condition
passes will be generated CDR files.

2.8 ZUF-06-02-005 Bx Interface Supports FTP

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP32.251, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298

Implemented in: ZXUN CG

2.8.1 Summary
Bx Interface refers to the CDR file transfer interface from CG to the Billing System. CG
supports FTP over TCP/IP in Bx Interface.

2.8.2 Benefits
CG supports FTP protocol to distribute the charging data to the Billing Systems or other
downstream systems. CG acts either as initiator or responder.

2.8.3 Description
Files can be transferred to the BS in one of the following modes:

 Push mode

10 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

In this transfer mode the CDR files are written from the CGF to the B S at a time and/or
frequency controlled by the CGF. I.e. the CGF pushes the files to the BS. This implies
that the CGF operates in client mode and the BS in server mode.

In push mode CG can distribute the same CDR files both to a billing system and to other
downstream systems at the same time.

If the file transfer fails, the CGF should properly reflect this in an error log and generate
appropriate alarms.

CG supports Buffering, that is in case of a link failure, the detail records are buffered on
disk array and sent automatically as soon as it is possible to distribute to the business
system again.

 Pull mode

In this transfer mode the BS reads the CDR files that are available in the appropriate
CGF directories. The time and/or frequency of the file transfer are controlled by the BS.
I.e. the BS pulls the files from the CGF. This implies that the CGF operates in server
mode and the BS in client mode.

In this mode, the BS needs to delete the file that is transfer successful. If the file is not
transmitted over a period of time, the CGF would reflect this in an error log and generate
appropriate alarms.

CG supports Buffering, that is in case of a link failure, the detail records are buffered on
disk array and sent automatically as soon as it is possible to distribute to the business
system again.

2.9 ZUF-06-03-001 O&M Functions

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.9.1 Summary
The O&M Functions include Security Management, Configuration Management,
Performance Management, and Fault Management.

2.9.2 Benefits
The operator can use this feature freely and manage the CG system well.
 ZXUN CG Feature List

2.9.3 Description

All O&M functions are provided by the GUI based on Web or Java.

CG can support user management. Two user levels, administrator and common user,
are defined and supported. The administrators have complete and unrestricted access to
all the system functions including user add, user edition, user deletion, and user rights
assignment. The common users only have the rights assigned by the administrators.
This functionality can be conducted on the LMT

CG supports configuration management. The common operation parameters can be

configured on the LMT. Configuration infomatioin can be export to file or import
from file.

CG supports performance management. The hardware supervision keeps track of

system resource usage. This includes CPU, RAM, disk, and I/O resources. The number
of CDRs that processed by CG can be monitored and also displayed on the LMT.

CG supports fault management. The fault management presents and records the
software and hardware faults as well as the important events by the means of notice and
alarm, informs users timely and accurately, so as to locating and solve the faults. It also
provides such methods as filter, confirm, delete and query to define the alarming notice
management. In addition, it provides the basic operational man-machine commands
such as reset and restore etc.

In case of the fault detected by the CG process, the alarm information, which includes
the alarm code, alarm cause code, alarm type, alarm time, fault place, fault details, etc,
is sent to the alarm collection process in the OMM, alarm management provides the
functions of:

 Detecting and reporting system error and abnormal data of ZXUN CG in real time.

 Start failure of application process

 Disconnection with NEs and Billing System

 Insufficient hard disk space and hard disk failure

 CPU and memory overload

 Switch triggered between active equipments and standby ones

 File R/W failure and file transfer failure.

 Giving a sound alarm by an alerting box.

 Giving an advice when there is an alarm to facilitate an O&M operator to locate the
problem and repair the system.

12 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

During the fault recovery, the alarm-generated process in CG will send the
corresponding recovery message to the alarm collection process in the OMM. The alarm
recovery message has the same structure as the alarm message, except the generation
time should be recovery time. Instead of contained in the source alarm information, the
alarm level is generated by the alarm process according to the check table of alarm code
and alarm level. The fault recovery has two modes: automatic recovery and manual
recovery. Some faults such as threshold override can be recovered automatically, but
some faults such as software error requires the manual intervention to recover.
Whichever mode is adopted, the corresponding alarm should conduct the recovery
processing after the fault recovery.

The notice information is generated by the CG service process, informing the OMM of
the events and unimportant and instant abnormities. There is no corresponding recovery
event for the notice, the source data structure of the notice is the same as the alarm.

CG supports log management. The operation log contains information about the user
commands sent from the CG client to the CG server process. The operation log keeps
track of commands that modify the state of the CG server. It is possible to retrieve the
time when the command was issued and by whom.

CG can use Simple Network Management Protocol (SNMP) to distribute, and cease
alarms to external surveillance systems, for example, network management systems.

2.10 ZUF-06-03-002 System Security

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.10.1 Summary
The System Security feature consists of a number of functions that can be divided into
the following main areas:

 Hardware server security -- redundant server solution.

 Network security -- security functions in the network, hardware and OS.

 Client security -- user authentication on OS level and CG level.

 Reliability -- functions that assures the continuous work, and consistency of CG

itself.

 Communication -- functions to handle communication problems when collecting and

distributing CDRs.
ZXUN CG Feature List

 Data consistency -- functions to ensure that no data is lost, duplicated or erroneous.

2.10.2 Benefits

The user can use this feature to reduce the software-attributed or hardware-attributed
outage. It enables users to execute maintenance without the need of powering off the
whole system, such as hardware changing, software upgrading, thus ensuring the high
performance, high reliability and high availability of the system, and preventing the loss
of the charging data undesirable.

2.10.3 Description

 Redundant servers

CG employs the high-performance ATCA platform and the cluster technology. The
redundant server solution consists of two hardware servers, one primary and one
secondary. Both servers must have the same configurations and have connections to all
the NEs in the network.

The Service Processing Unit software of the CG installed on both servers but only one
server is running on at a time. The running server is the active server while the other is
the standby server. When the active server becomes faulty, the Service Processing Unit
software of the CG will be completely switched over to the standby server and continue
the operation.

 Network Security

Each server needs to provide two Ethernet interfaces for cluster interconnection, which
forms a private network among different nodes in the cluster to transfer heartbeat
information. Of two private connections, only one is used, with the other as redundancy
backup.

Relative to the private network interface of the cluster interconnection, each server also
has a public network interface providing services to the external equipment. The SPU
connects to the three different external objects: OMM, IMS NEs and Billing System.
Different GE network interfaces are used for them.

CG supports secure charging data transfer using SFTP over TCP/IP. In brief, SFTP is a
secure version of FTP, which allows the user (client) to encrypt the identity and the data
transferred over a network. Technically, FTP and SFTP are two entirely different
protocols, however from the viewpoint of functionality they are similar. SFTP uses
Secure Socket Layer (SSL).

 Client Security

To gain access to the CG, the user must login, by specifying a user-id and password.
The following parameters are configurable for users:

14 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

Minimum password length:It is possible to set a minimum required length of the users
password.

Password expiry:It is possible to set a maximum duration time in days for the passwords
if the password expiry function is turned on.

Password strength: the strength of user passwords can be set, if a strong password, the
password need to include the following three categories characters in four categories :
numbers, lowercase letters, uppercase letters and special characters.

 Reliability

High availability is gained by means of consolidation of hardware and software features.

In terms of hardware, redundant cluster interconnections, shared disks and public
network interface can prevent the occurrence of single-point failures. The cluster
software monitors uninterruptedly the status of member nodes and keeps faulty nodes
from joining the cluster, thus preventing data damages. In addition, the cluster monitors
the Service Processing Unit (SPU) software of the ZXUN CG and related system
resources and implements failure switching or restarts the SPU software of the ZXUN
CG when it detects any fault.

Each server is equipped with a local hard disk for the installation of the OS, and CG
software, local hard disk with RAID1 will ensure the security of the operating system and
the software.

The data generated by the CG, such as CDR files and database files, are stored on the
shared IP-SAN disk array and are accessible to both servers. The shared disks are
installed in the disk array, which is connected to the two servers via network cables. The
RAID10 plus hot spare will ensure the security of CDR files even if one of hard disks is
damaged.

 Communication security

If it is not possible to distribute detail records, CG buffers the CDR files on disk array and
sends them automatically as soon as it is possible to distribute to the business system
again. This means that all data buffered in CG, all configurations, all logs and all alarms
are kept in safe storage on the disk array.

CG supports alternative routing of charging information when distributing. This can be

useful in case a business system fails to respond on a request for communication from
CG. It is possible to configure CG to choose an alternative destination to deliver the
charging information. If the primary business system is not reachable, CG will raise an
alarm to notify this to the user.

 Data consistency

The duplicate check eliminates the risk of double charging for events in the operators
network
ZXUN CG Feature List

CG supports Sequence number validation, the Sequence number check makes it

possible to examine if all CDRs have been received in the correct order and that no
CDRs are missing.

 System Security Guide

In the user documentation, a set of documents are included that contain guidelines that
describe how to perform OS hardening and how to verify that the system is protected
against attacks from other systems.

 Port settings

All used communication ports are configurable, where applicable. It is for instance
possible to configure the ports used for communication between the CG client and the
CG server.

2.11 ZUF-06-03-003 SNTP Support

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

2.11.1 Summary
CG used SNTP (Simple Network Time Protocol) client to synchronizing the clocks of CG
from NTP/SNTP server in the network.

2.11.2 Benefits
SNTP is used to implement very precise timekeeping in order to avoid run-time errors
and data corruption.

2.11.3 Description
CG used SNTP client to synchronizing the clocks of CG from NTP/SNTP server. The
version of SNTP that CG supported is v3. The IP address of NTP/SNTP server is
configurable.

16 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

3 Optional Features

3.1 ZUF-06-04-001 CDR Query

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP32.251, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298

Implemented in: ZXUN CG

3.1.1 Summary
Provide the functions of CDR Browse and Query.

3.1.2 Benefits
The operator uses this feature browse or query CDR content; all functions are provided
by the GUI based on Java.

3.1.3 Description
CG provides the following functions:

 CDR Browse: Display the CDR contents as text format. It enables the operator to
browse the field contents in the CDR files quickly.

 CDR Query: Query the CDR as per the preset condition and display the result in
text. This function is used to analyze CDR files so as to provide the maintenance
and technical personnel with the convenient troubleshooting method. This way
makes inquiring files output state more convenient in debugging and station
preconstruction phase, finding the mistakes in traffic process, so as for further
resolving.

 Offline CDR Browse and Query: Browse and Query the CDR contents of CDR files
in the local hard disk and without logon CG.

3.2 ZUF-06-04-004 CDR Routing

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

 ZXUN CG Feature List

3.2.1 Summary

CDR routing function can distribute CDR to different directory according to different
conditions, to facilitate billing system for processing.

3.2.2 Benefits

CDR routing functions are used in order to control the data flow through CG. Operator
can decide how the CDR streams should be routed from CG towards the Billing Systems
or other application system.

3.2.3 Description

The CDR are classified into the appropriate directory based on a field, or combination of
fields, directory name can be configured, called the channel. Different CDR channels
can be sent to different billing system or statistical system, a channel can send to
multiple billing system or statistics system.

3.3 ZUF-06-04-005 Customized CDR Format

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

3.3.1 Summary
CG provides customized formats for operators as their requirements.

3.3.2 Benefits
CG can provide the coding/decoding format as the requirement of the Billing System,
thus avoiding the interface changing of the Billing System. This means shorter time for
introducing new services on the market and shorter time for making adaptations for the
operators.

3.3.3 Description
CG can be processing CDRs to:

 Translate CDRs from one format to another.

 Modify individual fields in CDRs.

18 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

 Enrich CDRs with new data.

 Remove unwanted data and fields.

CG can be used to transform the incoming CDRs into formats, and structures, that can
be handled by the downstream systems.

CG can encode CDRs to the following formats:

 BER

BER-encoded detail records.

 ASCII

ASCII-encoded detail records. Both fixed-size and token separated encoding is

supported.

CG can store the CDRs into files with the following file-formats:

 Blocked

Blocked files, where a file consists of several fixed size blocks. Each block contains a
number of detail records. The user configures the block-size.

 Non-blocked

Non-blocked files containing detail records.

 Header-Trailer

Files consisting fixed size headers and trailers. Headers and trailers are supported on
file-, block-, and detail record level.

3.4 ZUF-06-04-007 Bx Interface Supports SFTP

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP32.251, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298

Implemented in: ZXUN CG

3.4.1 Summary
Bx Interface refers to the CDR file transfer interface from CG to the Billing System. CG
supports SFTP over TCP/IP in Bx Interface.
 ZXUN CG Feature List

3.4.2 Benefits

CG supports SFTP protocol to distribute the charging data to the Billing Systems or
other downstream systems. CG acts either as initiator or responder

3.4.3 Description

SFTP protocol offers a secure file transfer. Files can be transferred to the BS in one of
the following modes:

 Push mode

In this transfer mode the CDR files are written from the CGF to the B S at a time and/or
frequency controlled by the CGF. I.e. the CGF pushes the files to the BS. This implies
that the CGF operates in client mode and the BS in server mode.

In push mode CG can distribute the same CDR files both to a billing system and to other
downstream systems at the same time.

CG also supports alternative destination that is definition of an alternative route to a

business system, in case of link failure.

If the file transfer fails, the CGF should properly reflect this in an error log and generate
appropriate alarms.

CG supports Buffering, that is in case of a link failure, the detail records are buffered on
disk array and sent automatically as soon as it is possible to distribute to the business
system again.

 Pull mode

In this transfer mode the BS reads the CDR files that are available in the appropriate
CGF directories. The time and/or frequency of the file transfer are controlled by the BS.
I.e. the BS pulls the files from the CGF. This implies that the CGF operates in server
mode and the BS in client mode.

In this mode, the BS needs to delete the file that is transfer successful. If the file is not
transmitted over a period of time, the CGF would reflect this in an error log and generate
appropriate alarms.

CG supports Buffering, that is in case of a link failure, the detail records are buffered on
disk array and sent automatically as soon as it is possible to distribute to the business
system again.

20 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

3.5 ZUF-06-04-008 CDR Merging for IMS Domain

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

3.5.1 Summary
As the front system of Billing System, CG provides the CDR merging function to merge
the Partial CDRs of an IMS Session into one CDR and export to the Billing System.

3.5.2 Benefits
This feature reduces the number of the CDRs which is sent to billing center, so as to
weaken the requirement for bandwidth of billing center transmission circuit and lighten
the processing burdens of the Billing System.

3.5.3 Description
In the IMS network, for a long-time session, there will be multiple Partial CDRs of a
same Session produced.

CGF provides the merging function. It merges the multiple Partial CDRs of a same
Session. The merging is based on:

ICID: At each SIP session establishment a new, session specific ICID is generated at
the first IMS network element that processes the session-initiating SIP INVITE message.
This ICID is then used in all subsequent SIP messages for that session until the session
is terminated.

Session ID: The Session identification. For a SIP session the Session-ID contains the
SIP Call ID.

Node Address: The address of the node providing the information for the CDR. This may
either be the IP address or the FQDN of the IMS node generating the accounting data.

Role of node: indicates the role of the IMS node, such as originating and terminating.

According to the ICID, Session ID, Node Address, Role of node, ZXUN CG can merge
these Partial CDRs which belong to one session into one CDR.
 ZXUN CG Feature List

3.6 ZUF-06-04-009 CDR Consolidation

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

3.6.1 Summary
The CDR Consolidation feature makes it possible to combine several CDRs into one
complete CDR. It is possible to collect data produced in several different network
elements, and combine them into one chargeable record corresponding to a complete
session.

3.6.2 Benefits
Taking advantage of the CDR consolidation feature, it is possible to create new CDRs
based on the collected information and distribute one single, enriched CDR including all
information required for charging. The consolidation can also used to decrease the data
volume that is distributed towards the Billing Systems since several collected CDRs are
consolidated into one distributed CDR.

3.6.3 Description
The consolidation feature provides possibilities for making any kind of combination of
CDRs.

The consolidation feature is based on the concept of retaining a pool of unconsolidated

and partially consolidated CDRs in a consolidation table. Each stored CDR has an
associated unique key. Every new incoming CDR is then checked against the
consolidation table for possible matches. This key is used when performing various
operations on the table, for example search or remove.

When a subscriber uses IMS services, for example making a call, CDRs will be
produced in several different IMS nodes involved including P-CSCF, S-CSCF, MMTel
AS, normally these CDRs will be distributed toward the Billing Systems directly, but if
this feature is activated, the CG system will combine them into one chargeable record
corresponding to a complete call or session.

3.7 ZUF-06-01-001 Ga Interface

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP32.251, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298

22 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

Implemented in: ZXUN CG

Commercial Attention: None

3.7.1 Summary

The Ga is the reference point from the Charging Data Function (CDF) to the Charging
Gateway Function (CGF), which is intended for the transport of Charging Data Records
(CDRs).

3.7.2 Benefits

Via Ga interface, CG collects CDRs generated by CDF in real time.

3.7.3 Description

Ga interface is the standard interface between CDF and CGF, and is used for CDR
transfer via the GTP’ protocol. Via Ga interface, CGF collects real-time CDRs generated
by multiple CDF, and support CDR redirection and duplicated CDR prevention.

As the extension of GTP, GTP’ is used for the billing data transfer at the interface
between CDF and CGF (Ga interface). GTP’ protocol possesses the following functions:

1 CDR-transfer mechanism between CDF and CGF.

2 Redirection of CDR transferring to another CGF.

3 Ability to detect communication failures between the communicating peers.

4 Using echo messaging.

5 Ability of a CDR handling node to advertise to peers about its CDR transfer.

6 Ability to prevent duplicate CDRs that might arise during redundancy operations to
reduce the number of the duplicated CDRs sent to the BS.

As illustrated in Figure 3 -3, the CDF - CGF communications are carried out using GTP'
over UDP/TCP and IP.
 ZXUN CG Feature List

Figure 3-3 Protocol Layer Relation between CDF and CGF Entities

The bearer protocol of GTP’ is TCP or UDP. Whether it is TCP or UDP, the protocol port
number of GTP’ is the reserved port number 3386 by default, and it is also configurable
and can be selected according to the actual situations. The source port number of UDP
is distributed by the originating party. Once the port number is decided, the source port
number of the terminating party is the same as the destination port number of the
originating party. In case of TCP protocol adopted, the port distribution is the same as
UDP.

CG supports standard GTP’ V0/V1/V2 based on TCP or UDP operating on Ga interface

to communicate with CDF, And CG can automatically identify the GTP’ version used by
CDF.

3.8 ZUF-06-01-002 GTP’ Protocol Tracing

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP32.251, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298

Implemented in: ZXUN CG

Commercial Attention: None

3.8.1 Summary
Trace GTP’ protocol signaling in real time via Ga interface

3.8.2 Benefits
With GTP’ protocol tracing function, the GTP’ protocol messages interworking between
CGs can be traced respectively by means of the GSN node. The GTP’ protocol tracing is

24 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

 ZXUN CG Feature List

mainly used to analyze signaling, provide operators with message tracing display,
provide maintenance and technical personnel with the facilitator, fault location method,
facilitate the signaling flow querying during debugging and commissioning, detect the
error in signaling interworking for the further processing.

3.8.3 Description

The GTP’ protocol trace falls into two parts in terms of fulfillment structure: signaling
transfer part and signaling display part. The signaling transfer part functions to collect
the signaling messages and send the message data to background, namely, client.
Running on Windows operating system, the client analyzes the message data and
provides the analyzing result to the operator via the GUI interface. The GTP’ protocol
tracing will not establish process on local NM Server, instead, the client will connect
directly with CG network elements, so as to conduct message interaction and implement
the GTP’ protocol tracing. The relation between the client and the Ga interface process
of the connected CG is shown as Figure 3 -4:

Figure 3-4 Interaction mode between modules in GTP’ signaling tracing system

3.9 ZUF-06-01-006 Diameter Protocol Tracing

Specification: 3GPP 22.115, 3GPP 32.240, 3GPP 32.260, 3GPP 32.295, 3GPP 32.297,
3GPP 32.298, 3GPP 32.299

Implemented in: ZXUN CG

3.9.1 Summary
Trace the diameter protocol signaling of Rf interface in real time.

3.9.2 Benefits
With diameter protocol tracing function, the diameter protocol messages interworking
between CGs can be traced respectively by IMS node. The diameter protocol tracing is
mainly used to analyze signaling, provide operators with message tracing display,
provide maintenance and technical personnel with the facilitator, fault location method,
 ZXUN CG Feature List

facilitate the signaling flow querying during debugging and commissioning, detect the
error in signaling interworking for the further processing.

3.9.3 Description

The diameter protocol trace falls into two parts in term of fulfillment structure: signaling
transfer part and signaling display part. The signaling transfer part functions to collect
the signaling messages and send the message data to background, namely, client.
Running on Windows operating system, the client analyzes the message data and
provides the analyzing result to the operator via the GUI interface. The diameter protocol
tracing will not establish process on local NM Server, instead, the client will connect
directly with CG network elements, so as to conduct message interaction and implement
the diameter protocol tracing. The relation between the client and the Rf interface
process of the connected CG is shown as Figure 3 -5:

Figure 3-5 Interaction mode between modules in Diameter signaling tracing system

26 © 2022ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary