Oracle Communications Operations Monitor creates Diameter Transaction Records (TDR files) in CSV format. The files are placed in the tdr/ directory under the FTP/FTPS root. The TDR files have the following format:
tdr-unix_timestamp-sequence.csv
where:
unix_timestamp is the Unix timestamp when the file was created.
sequence is a number monotonically increasing.
The files are rotated when they reach their maximum size (10000 records). When a CSV file is finished, another empty file having the following format is created:
tdr-unix_timestamp-sequence.csv.FIN
Several times per day, old TDR files are compressed to files having the following format, while the corresponding uncompressed files are deleted:
tdr-unix_timestamp-sequence.csv.gz
The recommended way of gathering the TDR files is to connect via FTP/FTPS, copy and delete all the files ending in csv.gz. Alternatively, to get the TDR data in near real time, the MDR files that have a corresponding .FIN file can be copied and deleted.
Operations Monitor automatically limits the size of the tdr/ directory to 5 GB, by deleting the oldest files.
Table 13-1 lists the fields present in the generated CSV files:
| Field | Description |
|---|---|
|
application-id |
The IANA assigned Application Identifier of the Diameter transaction. The possible values as defined in RFC 5516 are outlined below:
|
|
command |
A human readable string describing the Diameter command-code. Can be one of the following:
|
|
command-code |
The Diameter command code of the transaction. For example for the command UPDATE_LOCATION the code would be 316. All the possible codes are defined in 3GPPTS 29.272 at the interface commands for S6a/S6d and S13. |
|
destination-realm |
Contains the realm the messages of a Diameter transaction should be routed to. |
|
dst-dev-id |
Identifier of the destination Diameter device. |
|
dst-ip |
Destination IP address of the Diameter transaction. |
|
duration |
The duration of the transaction in seconds (with a precision of microseconds), from the time the request is received to the time the transaction completes. |
|
IMEI |
IMEI value of the user. |
|
internal-id |
Unique internal identifier used by Operations Monitor to identify Diameter transactions. |
|
msisdn |
The msisdn number of the Diameter transaction identifying the subscription to a mobile network. |
|
network-access-mode |
Describes the networks that the user is registered to. Values range from 0 to 2. |
|
network-access-mode-text |
Describes the networks that the user is registered to. Possible values can be one of the following:
|
|
origin-realm |
Contains the realm of the originator of the Diameter messages of this transaction. |
|
rat-type |
A numeric code used to identify radio access technology that is serving the UE. Defined in TS 29212 at section 5.3.31. |
|
realm-ids |
Diameter transaction realm ID - not currently exported. |
|
result |
Human readable string of the result code. |
|
result-code |
The numerical value of the Result-Code of the diameter transaction. For example 2001 for DIAMETER_SUCCESS. For all possible values refer to the standards. |
|
session-id |
A string with the Session-ID AVP of the Diameter transaction. |
|
src-dev-id |
Identifier of the source Diameter device. |
|
src-ip |
Source IP address of the Diameter transaction. |
|
start_ts |
Time value for the transaction request. |
|
stop_ts |
Time value for the transaction response. |
|
timestamp |
Unix timestamp of the start of the transaction. |
|
user-name |
IMSI used to identify the user of the Diameter transaction. |
|
visited-plmn-id |
The decoded visited PLMN ID found in the transaction with the 3 digit Mobile Country Code (MCC) and 2 or 3 digit Mobile Network Code (MNC) as defined in TS 123000 at section 12.1. |