PCRF CDRs
PCRF CDRs are generated to record rules handling sessions which includes start
, interim
, and stop
per session.
PCRF CDRs contain a fixed part section as well as a variable part. The variable part is optional. See PCRF CDR variable part for more details. |
Field | Name | Description | ||||
---|---|---|---|---|---|---|
1 |
|
The MSISDN of the subscriber in Tango internal format. |
||||
2 |
|
The service ID. This is set to 28 for the PCRF rules handler. |
||||
3 |
|
Indicates the transaction type. options
|
||||
4 |
|
Alphanumeric string that displays the ID of the network operator for which the CDR was produced. |
||||
5 |
|
The instance number of the PCRF rules handler service logic state machine that is handling the session. |
||||
6 |
|
The PCRF session termination reason.
values
|
||||
7 |
|
The failure code. It will fail for one of the following reasons: PCRF failure
SPR failure
PCEF rules failure
Session context store failure
|
||||
8 |
|
The value of the AVP of the same name in the CCR-T.
|
||||
9 |
|
Indicates the SPR error which is returned over the Sp interface in response to an Sp request. values
|
||||
10 |
|
The SPR dialogue termination result. values
|
||||
11 |
|
The response code which is returned from the DPS in response to a discount lookup request.
dps values
internal values
|
||||
12 |
|
The response code that is returned from the DS service in response to a scheduled discount lookup request.
ds values
internal values
|
||||
13 |
|
The date the CDR was generated. Format: |
||||
14 |
|
The time the CDR was generated. Format: |
||||
15 |
|
The CDR sequence number. This increments (from 0) for each CDR output for a given PCRF rules session. |
||||
16 |
|
Denotes the CDR segment. The segment counter increments from 0.
|
||||
17 |
|
The IP address assigned to the subscriber’s mobile equipment. |
||||
18 |
|
The IMEI from the subscriber’s user equipment if provided over the Gx interface. |
||||
19 |
|
The PDN ID decoded from the Gx Called-Station-Id or Rx session APN.
|
||||
20 |
|
The IP-CAN type passed by the PCEF over the Gx interface. options
|
||||
21 |
|
The RAT type passed by the PCEF over the Gx interface. |
||||
22 |
|
The AN-GW address if received from the PCEF over the Gx interface. |
||||
23 |
|
The SGSN address if received on the Gx interface from the PCEF. |
||||
24 |
|
The PLMN ID decoded from the Gx-GGSN-MCC-MNC. |
||||
25 |
|
The location information from the Gx 3GPP-User-Location-Info.
|
||||
26 |
|
The RAI if received on the Gx interface from the PCEF. |
||||
27 |
|
The reasons for the rules session udpate. causes
|
||||
28 |
|
The PCEF event trigger ID related to the rule update requests from the PCEF.
possible values
|
||||
29 |
|
The appplication identifier from the Rx AF-Application-Identifier.
|
||||
30 |
|
The Rx session ID for the application function interface.
|
||||
31 |
|
The Gx session ID for the PCEF interface. |
||||
32 |
|
The Gx Charging ID decoded from the Gx Access Network Charging Identifier Gx. |
||||
33 |
|
The Rx application function session start time. Format:
|
||||
34 |
|
The Rx session duration (in seconds). |
||||
35 |
|
The time that the PCEF (Gx) session started. Format: |
||||
36 |
|
The PCEF (Gx) session duration (in seconds). |
||||
37 |
|
The time that the PCRF rule handling session started. Format: |
||||
38 |
|
The time to wait (in milliseconds) for a profile response from the SPR. This will either be the actual time of the response or a timeout value in the case of a |
||||
39 |
|
The PCRF rule handling session duration (in seconds). |
||||
40 |
|
The total volume usage reported by the PCEF.
|
||||
41 |
|
The total volume usage sent to the SPCM.
|
||||
42 |
|
The total amount of time usage reported by the time metering service logic.
|
||||
43 |
|
The total amount of time usage sent to the SPCM.
|
||||
44 |
|
The total volume for the session that the SPCM has counted and acknowledged.
|
||||
45 |
|
The cell (mobile) load percent if there is a DPS response. This is an intger between
|
||||
46 |
|
The UEM profile key.
|
||||
47 |
|
The requested APN Aggregate Max Birate (AAMBR) DL AVP. This is adjusted based on the
|
||||
48 |
|
The authorised AAMBR.
|
||||
49 |
|
The subscriber plan state as received from the SPCM. This indicates whether the subscriber has a valid bundle. possible values
|
||||
50 |
|
Denotes the MS Timezone. This is expressed in 15 minute intervals from the UTC. time sample
Logic: Taking 0x4A00 from the sample CDR, we get (0x4A & 0x08) != 0 so it is a negative offset. 0x4A)>>4 + 10*(0x4A & 0x7 ⇒ 4 + 10*2 ⇒ 24 multiples of 15 minutes ⇒ 24/4 = 6.
|
||||
51 |
|
The UE prefix for IPv6. |
||||
52 |
|
The ANGW address for IPv6. |
||||
53 |
|
The SGSN address for IPv6. |
||||
54 |
` ` |
Empty field for future use. |
||||
55 |
` ` |
Empty field for future use. |
||||
56 |
` ` |
Empty field for future use. |
||||
57 |
` ` |
Empty field for future use. |
||||
58 |
` ` |
Empty field for future use. |
||||
59 |
` ` |
Empty field for future use. |
PCRF CDR variable part
The variable part is included after the fixed part and contains information about the PCC rules installation, usage reports and rule removal. The variable part of the CDR may include 2 parts for the same rule. The 1st part is for the usage reporting and the 2nd part is for the rule removal.
If there is no data to record, only the terminating element will be displayed. |
It contains zero or more elements and a terminating element.
Each field in the variable part is separated by a semi-colon (;) whereas the elements are separated by an ampersand (&). |
The terminating element is as follows (0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0) .
|
Name | Description | ||
---|---|---|---|
|
The name of the installed PCC rule. |
||
|
The precedence number of the PCC rule. |
||
|
The PCC rule type. possible values
|
||
|
The type of event which applies to the variable part. possible values
|
||
|
The name of the plan from which the PCC rule came. |
||
|
An integer used to identify the service flow.
|
||
|
The service flow status. possible values
|
||
|
The minimum uplink speed in bps.
|
||
|
The maximum uplink speed in bps.
|
||
|
The minimum downlink speed in bps.
|
||
|
The maximum downlink speed in bps.
|
||
|
The rating group for the PCC rule.
|
||
|
The SP Usage key for the PCC rule.
|
||
|
The Gx Monitory key for the PCC rule. |
||
` Usage Metering Type` |
The metering type for the rule. possible values
|
||
|
The usage report status code for the particular Gx monitory key. returned from SPCM
internal
internal-not-processed
|
||
|
Amount of usage reported by PCEF for this rule.
|
||
|
The percentage discount applied to the usage. range
|
||
|
The discount type. possible values
|
||
|
The amount of usage sent to the SPCM for the rule. This includes any discounts applied to the reported usage.
|
PCRF CDR samples
This section shows PCRF samples including:
PCRF Start Session
00041000060200000001010001,28,1,tenant,0,0,-1,-2,0,0,1,1,27/01/2015,04:53:14,0,-
2,0.69.16.170,354720058972287,tangotelecom.com,0,4,16.0.0.52,202.134.10.29,1
23456,0001020304050607,,0,-1,,,192.168.1.236:3860:1453870394:0,,,0,04:53:14,0,04:53:14,-1,0,0,0,0,0,0,-1,-1,-1,-1,-1,4a00,,,,,,,,,,&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Interim Install Rule
00041000080100000000000000,28,3,tenant,1,0,-1,-2,0,0,0,0,22/07/2014,10:54:20,1,-
2,85.0.0.0,013002002816836,tangotelecom.com,0,1002,16.0.0.52,0.69.16.11,9876
54,0001020304050607,123456ABCD01,0,-1,,,192.168.25.225:3869:1406022860:0,,,0,10:54:20,0,10:54:20,0,0,0,0,95,2,2000000,0,0,2000000,0,4a00,,,,,,,,,,&FACEBOOK;0;1;0;Addon1 Plan;-1;-1;65536;524288;131072;1048576;3;3-000002;01234567895f3235;-1;0;25;2;0&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Interim Remove Rule
00041000080100000000000000,28,3,tenant,1,0,-1,-2,0,0,0,0,22/07/2014,10:54:23,2,0,85.0.0.0,013002002816836,tangotelecom.com,0,1002,16.0.0.52,0.69.16.11,987654,0005060708091011,123456ABCD01,2,13,,,192.168.25.225:3869:1406022860:0,,,0,10
:54:20,3,10:54:20,-1,3,0,0,0,0,0,95,0,2000000,2000000,0,4a00,,,,,,,,,,&FACEBO
OK;-1;1;3;;-1;-1;-1;-1;-1;-1;-1;;;0;0;0;0;0&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Stop Session
00041000080100000000000000,28,2,tenant,1,0,-1,-2,0,0,1,0,22/07/2014,11:39:18,3,-
2,85.0.0.0,013002002816836,tangotelecom.com,0,1002,16.0.0.52,0.69.16.11,9876
54,0005060708091011,123456ABCD01,6,-1,,,192.168.25.225:3869:1406025555:0,,,0,11:39:15,3,11:39:15,0,3,0,0,0,0,0,95,0,2000000,170000,0,4a00,,,,,,,,,,&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Start VoLTE
00041008080001080404040609090706,28,101,tenant,18871,0,-1,-2,0,0,1,1,16/06/2019,19:54:07,17,-2,10.184.1.132,3567580831350318,,5,1004,202.134.10.39,202.134.10.39,47002,8274f020139474f02001fd3c0b,,4,-1,3gpp-service.ims.icsi.mmtel,sip:+8801844469976@ims.mnc002.mcc470.3gppnetwork.org;2955792278;1021;404,pbugw5.robi.com.bd;4095672873;121831424;13872,092e4e4e,19:54:07,0,19:49:28,279,19:49:28,-1,279,0,0,0,0,0,-1,-1,-1,-1,-1,4200,,,,,,,,,&DED-AUDIO-RULE1-2;0;0;0;;-1;2;-1;29000;-1;29000;3260;;;-1;-1;0;0;0;0&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Stop VoLTE
00041008080001080404040609090706,28,102,tenant,18871,0,-1,1,0,0,1,1,16/06/2019,19:52:32,15,-2,10.184.1.132,3567580831350318,,5,1004,202.134.10.39,202.134.10.39,47002,8274f020139474f02001fd3c0b,,4,-1,3gpp-service.ims.icsi.mmtel,sip:+8801844469976@ims.mnc002.mcc470.3gppnetwork.org;2955765434;1020;404,pbugw5.robi.com.bd;4095672873;121831424;13872,092e4e4e,19:49:39,173,19:49:28,184,19:49:28,-1,184,0,0,0,0,0,-1,-1,-1,-1,-1,4200,,,,,,,,,&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
PCRF Interim VoLTE
00041008080001080404040609090706,28,103,tenant,18871,0,-1,-2,0,0,1,1,16/06/2019,19:52:32,16,-2,10.184.1.132,3567580831350318,,5,1004,202.134.10.39,202.134.10.39,47002,8274f020139474f02001fd3c0b,,4,-1,3gpp-service.ims.icsi.mmtel,sip:+8801844469976@ims.mnc002.mcc470.3gppnetwork.org;2955765434;1020;404,pbugw5.robi.com.bd;4095672873;121831424;13872,092e4e4e,19:49:39,173,19:49:28,184,19:49:28,-1,184,0,0,0,0,0,-1,-1,-1,-1,-1,4200,,,,,,,,,&0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0