top button
Flag Notify
Site Registration

Is it possible to use Credit-Control-Failure-Handling in Gx interface?

+1 vote
234 views

Is it possible to use Credit-Control-Failure-Handling AVP in Gx interface. If so, how?

My query is when PCEF sends a CCRequest to PCRF and PCRF does not reply anything, so in that case will that be possible to use Credit-Control-Failure-Handling(CCFH) avp.

Does this behavior allowed as per 3GPP Standards or its upto the customization of the product. Any reference are highly appreciable.

posted May 3, 2016 by Chinmoy Padhi

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+2 votes

How PCEF decide which QCI_X(where X = 1,2,3,4,5,6,7,8,9,65,66,67,68,69,70) value need to be send to PCRF.
What is the significance of so many QOS-Class-Identifiers?
Even 3GPP 29.212 doesn't define any reason for classification between different QOS-Class-Identifiers.

+12 votes

Why do we require Gate Function ? I mean to say what is the need for this ? How Significant it is in Gx-Interface?

+1 vote

1) Assume that susbcriber is having lower specifications handset which can support of 300kbps in 2G radio, when susbcriber creates a session/starts browsing then GGSN will send QOS in CCR-I as 300kbps & PCRF will reply CCA-I as 400kbps (Assume that at PCRF end 400kbps plan is configured), subscriber can browse successfully & no extra messages in network

2) Assume that susbcriber is having lower specifications handset which can support of 300kbps in 2G radio, when susbcriber creates a session/starts browsing then GGSN will send QOS in CCR-I as 300kbps, PCRF will reply CCA-I as 400kbps (Assume that at PCRF end 400kbps plan is configured), subscriber can browse successfully, after sometime GGSN send CCR-U1 messages with event trigger revalidation timer expired & qos as 300kbps, PCRF will again execute policy function & allocate 400kbps in CCA-U1. Now GGSN again sends an CCR-U2 with 300kbps QOS-CHANGE as event trigger & again PCRF send 400kbps in CCA-U2, like this it go on loop.

/IPCANTYPE=3GPP-EPS mode/
Concern is why same qos send in case-1 is no loop messages, where as loop in case-2

+3 votes

I am trying to handle all the error scenarios seen while testing the Gx with the third party. As of now I had coded for just the successful scenarios.

I am looking for some of inputs on these error scenarios and how to proceed and exit gracefully (rather than crashing the code)

  • Dynamic rule config with wrong parameters., PGW sends CCR with the CCR type=TERMINATION_REQUEST. How can PCRF respond (just log error and comeout ?)

  • Static rule config with the "wrong rule name". When the PCRF sends CCA-I with the wrong rule name, PGW sends CCR-U with the Charging Rule Report with the "Rule-Failure-Code" as "Unknown Rule Name". In this case remove those rules and continue OR just comeout with just logging error)

+2 votes

Could you help me figure out CCRequest basic message contents sent from the PGW to PCRF. I am in a process of replacing our Gx interface from the static calls to the Diameter interface.

I am interested in any discussion about this interface.

I am also trying to understand , how the APN info is passed from the PGW(PCEF) to PGW. I think the Called-Party-AVP is used. It is bit contradicting info in the net than the one given in spec, (which says it is used to indicate Emergency APN)

...