GenericDB CDRs

The Generic Db process outputs CDRs whenever it handles a request to create/update/delete/query a record. These CDRs will be written to active_scs.cdr.

This section describes the fields that are contained in the CPS CDRs. The CDR will always contain the fixed part but can also contain an optional variable part. The following table describes the fields that are produced in the fixed part of the CPS CDRs.
Field Name Description

1

Subscriber ID

The MSISDN of the subscriber. This is in Tango internal format.

2

Service ID

The Tango service ID. This should be set to 48 for PCRF_SCS.

3

Transaction Type

Indicates the type of transaction for which the CDR is generated. The options are as follows:

options

  • 1 = Create

  • 2 = Update

  • 3 = Delete

  • 4 = Query

4

Tenant ID

Alphanumeric string that displays the ID of the network operator for which the CDR was produced.

5

Submission Date

The date that the request was submitted (in the format YYYY-MM-DD).

6

Submission Time

The time that the request was submitted (in the format HH:MM:SS).

7

Response Date

The date that the response was received (in the format YYYY-MM-DD).

8

Response Time

The time that the response was received (in the format HH:MM:SS).

9

CDR Correlation Key

A unique identifier to correlate different CDRs generated on the system.

This is set to the address of the PCRF rules handler which sent the request to the store.

10

Key Data

The Key data string that is used to key the record.

This is set to the Gx Session ID, the records within the store are keyed on the session ID.

11

ASCII Data

The ASCII string data to be persisted or queried.

This shall only be included if enabled via the configuration. The default configuration disables this feature

12

Octet Data

The Octet string data to be persisted or queried.

This shall only be included if enabled via the configuration. The default configuration disables this feature

13

Operation

The type of operation requested. The following operations are supported:

options

  • 0 = Create

  • 1 = Update

  • 2 = Delete

  • 3 = Query

14

Operation Result

The result of the lookup. There are two options:

options

  • 0 = lookup successful

  • -1 = lookup failure

15

Operation Error Code

The response string from the store. The following values are supported:

options

  • 0 = Store_OK

  • 1 = Store_N_Max_Records_Reached

  • 2 = Store_Nok_Max_Create_Fail

  • 3 = Store_Nok_Max_Update_Fail

  • 4 = Store_Nok_Max_Delete_Fail

  • 5 = Store_Nok_Max_Query_Fail

  • 6 = Store_Nok_Internal_Error

GenericDB CDR samples

This topic shows you Generic Db CDR samples including:

CREATE Request

Generic Db CREATE sample
00041000080100000000000000,48,0,VodafoneIE,2014-08-26,16:38:36.243,2014-08-6,16:38:36.243,dcoyle1/PCRF_rulesHandler/0/rulesHandlerSl/2:16030,192.168.25.225:3869:1409067516:0,,30820322800453fca9fca181b980060000000001...,0,0,0

QUERY Request

Generic Db QUERY sample
00041000080100000000000000,48,3,VodafoneIE,2014-08-26,16:39:36.238,2014-08-26,16:39:36.238,dcoyle1/PCRF_rulesHandler/0/rulesHandlerSl/0:16030,192.168.25.225:3869:1409067516:0,,30820322800453fca9fca181b980060000000001...,3,0,0

UPDATE Request

Generic Db UPDATE sample
00041000080100000000000000,48,1,VodafoneIE,2014-08-26,16:39:36.243,2014-08-26,16:39:36.243,dcoyle1/PCRF_rulesHandler/0/rulesHandlerSl/0:16030,192.168.25.225:3869:1409067516:0,,30820322800453fcaa38a181b980060000000001...,1,0,0

DELETE Request

Generic Db DELETE sample
00041000080100000000000000,48,2,VodafoneIE,2014-08-26,16:39:38.242,2014-08-26,16:39:38.242,dcoyle1/PCRF_rulesHandler/0/rulesHandlerSl/0:16030,192.168.25.225:3869:1409067516:0,,,2,0,0