Nokia Siemens Networks Flexi ISN, Release

3.2

CDR Storage for On-Demand

Transfer in Flexi ISN

DN70473096 © Nokia Siemens Networks 1 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
the use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The documentation has been prepared to be used by professional and properly
trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given “as is” and all
liability arising in connection with such hardware or software products shall be defined
conclusively and finally in a separate agreement between Nokia Siemens Networks and the
customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that
the instructions contained in the document are adequate and free of material errors and
omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,
explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Contents

Contents

Summary of changes .............................................................................5

1 CDR delivery to TXT- or XML formatted files.......................................7

1.1 How this mode is intended to be used .....................................................7
1.2 Files for text format disk storage ..............................................................7
1.3 Files for XML format disk storage.............................................................8
1.4 Accessing file storage ..............................................................................9
1.5 Changes to the TEXT/XML interface from previous releases ................10

2 Examples of CDR files .........................................................................11

2.1 Plaintext G-CDR.....................................................................................11
2.2 XML G-CDR ...........................................................................................11
2.3 Plaintext SA-CDR...................................................................................11
2.4 XML SA-CDR .........................................................................................12
2.5 Possible values for Diagnostics field ......................................................12
2.6 The cdr.dtd file........................................................................................16

Glossary ................................................................................................23

DN70473096 © Nokia Siemens Networks 3 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

4 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Summary of changes

Summary of changes
Changes in release 3.2 CD4
Changes in content
No changes in content.
Changes in documentation
Product names updated, no content changes.

Changes in release 3.2 CD2

Changes in content
High availability is supported in text and XML CDRs.
New CDR files are now opened in a temporary directory (previously a
temporary file was opened in the /var/tex/_CDRS directory).
Changes in documentation
Chapter 1 CDR delivery to TXT- or XML-formatted files: information has
been added that the CDR files are synchronized between the active and
standby management blades.
Chapters 1.2 Files for text format disk storage and 1.3 Files for XML
format disk storage: information about the temporary directory has been
added.

Changes between releases 3.1 and 3.2

Changes in content
G-CDRs:
• A new value added to the cause for record closing:
SGSN_CHANGE.
SA-CDRs:
• New field added: OCS result code.
• The change condition field can have several values.
• The following fields have been removed:
ƒ data content downlink
ƒ data content uplink
ƒ No OCS credit control
Changes in documentation
Chapter 1 CDR delivery to TXT- or XML-formatted files: a clarification
about CDR high availability has been added.

DN70473096 © Nokia Siemens Networks 5 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

Chapter 2 Examples of CDR files: the printouts of the SA-CDR and the
cdr.dtd files have been updated.
The ID number for this document has been changed to DN70473096
(previously DN70296451).

Changes in release 3.1 CD1

Changes in content
No changes in content.
Changes in documentation
Section 1 CDR delivery to TXT- or XML-formatted files: a clarification
about CDR high availability has been added.

Changes between releases 3.0 and 3.1

Changes in content
No changes in content.
Changes in documentation
Chapter 1.4 Accessing file storage has been added.
Chapter 2 Examples of CDR files has been restructured and the
printouts have been updated.

6 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
CDR delivery to TXT- or XML formatted files

1 CDR delivery to TXT- or XML formatted

files
This functionality is responsible for storing CDRs to the Flexi ISN
operation and maintenance (O&M) hard disk drive. When 'text' or 'XML'
is selected for the CDR generation mode, the CDR sender process
(ggsncs) does not use the Ga interface at all, and because the charging
gateways are not used there is no need to configure them.
The only difference between text- and XML-formatted files is the actual
format written to the disk file. Otherwise these two formats act exactly in
the same way.
CDR files (text and XML CDRS) are synchronised between the active
and the standby management blades, so if one of the management
blades fails, no CDRs are lost.

1.1 How this mode is intended to be used

The operator is responsible for both fetching the CDR files from the
corresponding Flexi ISN’s CDR directory and removing them after the
retrieval has succeeded. Failure to remove the old files can result in the
file system becoming full.

1.2 Files for text format disk storage

Text format CDR files are stored in the /var/txt_CDRs directory on the
Flexi ISN management blade. This directory will contain multiple CDR
files with plaintext CDR data in them. Each file can contain at most
10 000 CDRs (this is not configurable). After 10 000 CDRs have been
written to the file, the file is closed and a new file is opened. The file can
contain G-CDRs and SA-CDRs. When a CDR is generated by the Flexi

DN70473096 © Nokia Siemens Networks 7 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

ISN (independently of the type), it is written to the current file. There are
no G-CDR- or SA-CDR-specific files.
If you wish to see the CDRs right after they have been generated (for
example, during testing), change the CDR generation mode from text to
XML. This closes the CDR file.
When a new file is opened, a file name is reserved for storing the file.
However, the file is not directly opened with the real file name; instead, a
file is opened in a temporary directory with the name:
/var/ha_temp_txt_CDRs/.unfinished_cdr_output
When the file contains the maximum number of CDRs or the ggsncs
process is shut down, the file is renamed with its real name. This makes
it easier for operators to fetch finished files. The operator can, for
example through telnet, use the mget *.log.gz command to fetch the
finished files, and be sure that the operator is not accidentally fetching
the file currently being written.
The CDR file names are in the format cdr.<timestamp>.log.gz, where
<timestamp> is a unix timestamp, that is, the number of seconds since
epoch (January 1, 1970). As the name suggests, the log file is
compressed with libz when it is written to disk (libz is a library with
functions used to compress files). An example of this file is:
/var/txt_CDRs/cdr.1138111082.log.gz.
No other files are involved when CDRs are generated to text format.

1.3 Files for XML format disk storage

XML format CDR files are stored to the directory /var/XML_CDRs on the
Flexi ISN management blade. This directory contains multiple CDR files
with XML format CDR data in them. Each file can contain at most 10 000
CDRs (this is not configurable). After 10 000 CDRs are written to the file,
the file is closed and a new file is opened. The file can contain G-CDRs
and SA-CDRs. When a CDR is generated by the Flexi ISN
(independently of the type), it is written to the current file. There are no
G-CDR- or SA-CDR-specific files.
If you wish to see the CDRs right after they have been generated (for
example, during testing), change the CDR generation mode from XML to
text. This closes the CDR file.
When a new file is opened, a file name is reserved for storing the file.
However, the file is not directly opened with the real file name; instead, a
file is opened in a temporary directory with the name:
/var/ha_temp_XML_CDRs/.unfinished_cdr_output

8 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
CDR delivery to TXT- or XML formatted files

When the file contains the maximum number of CDRs or the ggsncs
process is shut down, the file is renamed with its real name. This makes
it easier for operators to fetch finished files. The operator can, for
example through telnet, use the mget *.log.gz command to fetch the
finished files, and be sure that the operator is not accidentally fetching
the file currently being written.
The CDR filenames are in the format cdr.<timestamp>.log.gz, where
<timestamp> is a unix timestamp, that is, the number of seconds since
epoch (January 1, 1970). As the name suggests, the log file is
compressed with libz when it is written to disk. An example of this file is:
/var/XML_CDRs/cdr.1138111082.log.gz.
In addition to the CDR XML files, the file /opt/ggsn/etc/cdr.dtd is
copied to the /var/XML_CDRs directory when the ggsncs process is
restarted or the XML CDR storage is first configured. This DTD file is
needed to parse the XML format of the CDRs.

1.4 Accessing file storage

FTP pull is a supported transfer method to fetch CDR files from the Flexi
ISN. To be able to log in as an FTP user, perform the following
instructions.
1. Create an FTP user and give a password that fulfils the
requirements for a new user.
For detailed instructions, see Chapter Adding users in Security and
Access Configuration in Voyager for IPSO 3.9.2NET.
2. Enable FTP.
For detailed instructions, see Chapter Enabling network access in
Security and Access Configuration in Voyager for IPSO 3.9.2NET.
3. Log in with the user name and password you just created.
Use something other than FTP (for example
SSH/Voyager/console).
4. Change the password as requested by the Flexi ISN.
5. Now you can log in using FTP.

DN70473096 © Nokia Siemens Networks 9 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

1.5 Changes to the TEXT/XML interface from previous

releases
• Files are compressed automatically
To save disk space, the files are automatically compressed when
written to disk using libz. This increases CPU usage of the ggsncs
process to around 30% during busy CDR generation times, but
increases the number of CDRs stored: roughly the compression
ratio for a typical file is from 18MB to 250kb.
• New file naming
Earlier Flexi ISN/GGSN versions used static file names with the
format cdr.<n>.log, where n was a number from 1 to 20. When the
last file was written, the first file was written over, which caused
CDR loss for some operators. Since Flexi ISN Release 3.0, the file
naming scheme does not overwrite any of these files, but can
cause the file system to fill up if the operator does not remove the
old files properly.
In addition, the currently written file is actually stored first with the
file name .unfinished_cdr_output, making it a hidden file for
operators. Only after the file has been closed and is ready will it
use the real file name, and the operator may safely fetch and
remove it.
• Interface initialisation
The interface itself can now be reliably opened and closed as
many times as desired.

10 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

2 Examples of CDR files

2.1 Plaintext G-CDR

The attached file below contains a table with the type name, text, and
value examples for a plaintext G-CDR.
plaintext G-CDR
The Location information field is composed of the characters CI or
SAI followed by four groups of numbers separated by a space. The
meaning of the four groups of numbers is the following (starting from the
group closest to the characters): MNC, MCC, LAC, and CI or SAI
(depending on the value of the characters).

2.2 XML G-CDR

The attached file below contains a table with the type name, text, and
value examples for an XML G-CDR.
XML G-CDR

2.3 Plaintext SA-CDR

The attached file below contains a table with the type name, text, and
value examples for a plaintext SA-CDR.
plaintext SA-CDR
The PDP type organisation field is always followed by the PDP type
value field, which is named as value in the plaintext CDRs.

DN70473096 © Nokia Siemens Networks 11 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

The Location information field is composed of the characters CI or

SAI followed by four groups of numbers separated by a space. The
meaning of the four groups of numbers is the following (starting from the
group closest to the characters): MNC, MCC, LAC, and CI or SAI
(depending on the value of the characters).
In the plaintext SA-CDRs, the change time at the CDR level is called
Close Time.

2.4 XML SA-CDR

The attached file below contains a table with the type name, text, and
value examples for an XML SA-CDR.
XML SA-CDR

2.5 Possible values for Diagnostics field

All the possible values for the Diagnostics field are listed below.

Access point not found

Max active PDP context count/AP exceeded
Max dynamic addresses/AP exceeded
No space for a new PDP context
Unverified mobile acceptance is not allowed at this AP
Attempting to create secondary PDP context with no primary
Successful
Unknown reason
Delete PDP context request
Primary access point reconfigured
Primary access point deleted
SGSN is unreachable
SGSN has been restarted
Mandatory information element missing from request
Mandatory information element is not correct in request
RADIUS authentication server can not be contacted

12 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

RADIUS accounting server can not be contacted

Static PDP address type not supported
Static PDP address is out of allowed range
PDP address is already in use by another PDP context
DHCP server can not be contacted
Failed to allocate address from internal address pool
No response from DHCP
DHCP lease is too short
DHCP lease can not be renewed
DHCP assigned new address to active PDP context
Bad IP address from DHCP
RADIUS authentication failed
RADIUS accounting failed
Bad IP address from RADIUS
Error indication from SGSN
Unknown dynamic address allocation method
GGSN is being shut down
TFT error
Admission refused
GGSN configuration changed
Session timer expired
Idle timer expired
L2TP server authentication failure
L2TP session failed
Bad IP address from L2TP
SGSN created new context over existing one
Update PDP Context request to SGSN has failed
Requested PDP address type not supported
Requested PDP address type not supported for requested
access point
Dynamic address allocation not supported for requested
access point
Secondary PDP context forcibly removed during intersystem
update
SGSN GTP version changed
L2TP server has given no IP address for the session

DN70473096 © Nokia Siemens Networks 13 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

ARP of the subscriber is too low

Out of bitrate capacity for realtime traffic
Out of bitrate capacity for conversational traffic
Out of bitrate capacity for streaming traffic
CPU load is too high
Traffic load is too high
IP address is missing from RADIUS Access-Accept; required
by AP
PDP context not found
RADIUS Server Disconnected
No memory for a new AP connection
Requested from portal CLI
No default services configured for cAP
Secondary PDP context is not allowed in service-aware
session
Information to select main sAP is missing from RADIUS
Access-Accept
Problems with NSM connection
NSM information for subscription has been updated
Problems with OSC connection or OSC response
Problems in GGSN configuration, check the log for details
No such service
Too many services per session
Problems with NSM response
OSC disconnected
SGSN assigned TEID user plane of this context to a new
context
Secondary PDP context is not allowed in OSC-prepaid session
User authentication over Go interface has failed
Revoke authorisation from PDF
Failure in PDF decision enforcement
Negotiated QoS is better than requested
Service profile for the session updated by RADIUS
This AP cannot be selected directly by MS
No accounting message received for NAS context
Collision of NSAPIs selected in GPRS network and by the AC
Network Access Server deleted

14 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

Network Access Server configuration changed

NAS RADIUS Accounting On received
NAS RADIUS Accounting Off received
NAS RADIUS Unknown Assigned Session Id
Secondary access point reconfigured
Secondary access point deleted
Bad or missing wallet-related parameters for a service
Inbound Roaming Restricted
Too many unanswered RADIUS Accounting requests at the
moment
Waiting for acknowledgement of the initial RADIUS
Accounting On
NAS did not supply essential attribute
Error in RADIUS user profile
Too many activations are in progress at the moment
Activation could not be completed within reasonable amount
of time
Delete request by HA master
HA attempted for context using online charging
Real time Primary PDP context activation not allowed to
access point
Stuck transaction during EUA database synchronisation
OCS was unreachable due to lack of transport connection
OCS did not respond within the time allowed
OCS sent a result code in the CCA indicating an error
OCS sent an incomprehensible CCA
OCS closed the PDP context with an Abort-Session-Request
OCS failure handling - continue action timeout
Database conflict in interface blade
User profile search request to NSM timed out
Support for this feature is not enabled
Licensed capacity exeeded
User profile is missing from NSM

DN70473096 © Nokia Siemens Networks 15 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

2.6 The cdr.dtd file

The file below must be placed in the same directory where the XML files
are placed so the corresponding browser can open and display the
contents of the XML files.

<?xml version="1.0" encoding="UTF-8"?>

<!-- DTD for the CDRs in Nokia(?)'s ISN3.2 -->

<!ELEMENT cdr (gcdr?, sacdr?)>

<!ELEMENT gcdr (g-id, g-data)>
<!ELEMENT sacdr (sa-id, sa-data)>
<!ELEMENT g-id (
record_type,
GGSN_address,
charging_id
)
>

<!ELEMENT g-data (
opening_time,
time_zone,
SGSN_address+,
sgsn_plmn_id,
g-container+,
duration,
cause_record_closing,
apn,
imsi?,
pdp_type,
charging_characteristics,
msisdn?,
pdp_address?,
node_id,
record_sequence_number,
dynamic_address_flag?,

16 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

diagnostics?,
apn_selection_mode,
charging_characteristics_selection_mode,
charging_profile,
charging_type,
charging_type_selection_mode,
session_id,
access_type,
icid?,
imei?,
FCI?,
location_info?,
ms_timezone?,
local_sequence_number,
cdr_stored?
)
>

<!ELEMENT g-container (
qos_negotiated?,
data_volume_uplink,
data_volume_downlink,
toll_free_data_uplink?,
toll_free_data_downlink?,
change_condition,
change_time,
time_zone?
)
>

<!ELEMENT pdp_type (
pdp_organisation,
pdp_value
)
>

DN70473096 © Nokia Siemens Networks 17 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

<!ELEMENT sa-id (
record_type,
session_id,
charging_id,
GGSN_address
)
>

<!ELEMENT sa-data (
SGSN_address,
sgsn_plmn_id,
qos_negotiated,
imsi?,
charging_characteristics,
msisdn?,
pdp_address?,
dynamic_address_flag?,
charging_characteristics_selection_mode,
charging_profile,
charging_type,
charging_type_selection_mode,
access_type,
duration,
apn,
apn_selection_mode,
pdp_type,
node_id,
icid?,
imei?,
diagnostics?,
location_info?,
ms_timezone?,
FCI?,
opening_time,

18 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

time_zone+,
sa-container+,
cdr_continues?,
close_time,
cause_record_closing,
record_sequence_number,
local_sequence_number,
cdr_stored?
)
>

<!ELEMENT sa-container (
service_id,
charging_class,
change_condition,
change_time?,
time_zone?,
data_volume_uplink?,
data_volume_downlink?,
data_content_uplink?,
data_content_downlink?,
hits_uplink?,
hits_downlink?,
duration?,
uplink_time?,
downlink_time?,
first_activity?,
last_activity?,
wallet_id?,
wallet_charging_type?,
no_OCS_cc?,
OCS_res_code?,
URL
)
>

DN70473096 © Nokia Siemens Networks 19 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

<!ELEMENT record_type (#PCDATA)>

<!ELEMENT GGSN_address (#PCDATA)>
<!ELEMENT charging_id (#PCDATA)>

<!ELEMENT opening_time (#PCDATA)>

<!ELEMENT time_zone (#PCDATA)>
<!ELEMENT SGSN_address (#PCDATA)>
<!ELEMENT sgsn_plmn_id (#PCDATA)>
<!ELEMENT duration (#PCDATA)>
<!ELEMENT cause_record_closing (#PCDATA)>
<!ELEMENT apn (#PCDATA)>
<!ELEMENT imsi (#PCDATA)>
<!ELEMENT charging_characteristics (#PCDATA)>
<!ELEMENT msisdn (#PCDATA)>
<!ELEMENT pdp_address (#PCDATA)>
<!ELEMENT node_id (#PCDATA)>
<!ELEMENT record_sequence_number (#PCDATA)>
<!ELEMENT local_sequence_number (#PCDATA)>
<!ELEMENT dynamic_address_flag (#PCDATA)>
<!ELEMENT diagnostics (#PCDATA)>
<!ELEMENT apn_selection_mode (#PCDATA)>
<!ELEMENT charging_characteristics_selection_mode
(#PCDATA)>
<!ELEMENT charging_profile (#PCDATA)>
<!ELEMENT charging_type (#PCDATA)>
<!ELEMENT charging_type_selection_mode (#PCDATA)>
<!ELEMENT session_id (#PCDATA)>
<!ELEMENT access_type (#PCDATA)>
<!ELEMENT icid (#PCDATA)>
<!ELEMENT imei (#PCDATA)>
<!ELEMENT FCI (#PCDATA)>
<!ELEMENT location_info (#PCDATA)>
<!ELEMENT ms_timezone (#PCDATA)>
<!ELEMENT cdr_stored (#PCDATA)>

20 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Examples of CDR files

<!ELEMENT qos_negotiated (#PCDATA)>

<!ELEMENT data_volume_uplink (#PCDATA)>
<!ELEMENT data_volume_downlink (#PCDATA)>
<!ELEMENT toll_free_data_uplink (#PCDATA)>
<!ELEMENT toll_free_data_downlink (#PCDATA)>
<!ELEMENT change_condition (#PCDATA)>
<!ELEMENT change_time (#PCDATA)>

<!ELEMENT pdp_organisation (#PCDATA)>

<!ELEMENT pdp_value (#PCDATA)>

<!ELEMENT cdr_continues (#PCDATA)>

<!ELEMENT close_time (#PCDATA)>

<!ELEMENT service_id (#PCDATA)>

<!ELEMENT charging_class (#PCDATA)>
<!ELEMENT data_volume_uplink (#PCDATA)>
<!ELEMENT data_volume_downlink (#PCDATA)>
<!ELEMENT data_content_uplink (#PCDATA)>
<!ELEMENT data_content_downlink (#PCDATA)>
<!ELEMENT hits_uplink (#PCDATA)>
<!ELEMENT hits_downlink (#PCDATA)>
<!ELEMENT uplink_time (#PCDATA)>
<!ELEMENT downlink_time (#PCDATA)>
<!ELEMENT first_activity (#PCDATA)>
<!ELEMENT last_activity (#PCDATA)>
<!ELEMENT wallet_id (#PCDATA)>
<!ELEMENT wallet_charging_type (#PCDATA)>
<!ELEMENT no_OCS_cc (#PCDATA)>
<!ELEMENT OCS_res_code (#PCDATA)>
<!ELEMENT URL (#PCDATA)>

DN70473096 © Nokia Siemens Networks 21 (23)

Issue 1-2
CDR Storage for On-Demand Transfer in Flexi ISN

22 (23) © Nokia Siemens Networks DN70473096

Issue 1-2
Glossary

Glossary
CDR Charging Data Record
CPU Central Processing Unit
DTD Data Type Definition
G-CDR GGSN Charging Record
GTP' Enhanced GPRS Tunnelling Protocol
ISN Intelligent Service Node
SA-CDR Service-Aware Charging Record
TLV Type-Length-Value
XML Extensible Markup Language

DN70473096 © Nokia Siemens Networks 23 (23)

Issue 1-2