top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

SPR: Is Sp interface with PCRF proprietary to an operator ?

0 votes
612 views

As per specification, PCRF has interface with SPR to get policy and charging rules for an user.
I want to know, whether implementation of this interface is operator dependent or not ? If answer is not then which specification contains the detail on Sp interface messages ?

posted Oct 3, 2018 by Vimal Kumar Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

This interface was defined in 3GPP TS 23.335 and TS 29.335.
For more details - https://www.developingsolutions.com/products/3g-network-testing/ud-interfacesp-interface/

answer Oct 3, 2018 by Althi Rajeswararao
Similar Questions
+3 votes
Information on the PCRF, mainly the Sp, Rx and Gx interface.

Looking for the information related to PCRF.

Another specific question. When the PCRF decides on a QOS and sends across to P-GW. P-GW might not have got any info related to Dedicated bearer to be established earlier. So how does it map this newly sent QOS for the new dedicated bearer to the one it requested by P-CSCF.

I am trying to understand, how to map the QOS info sent by PCRF to the "dedicated bearer request by the P-CSCF. Can PCRF on sending the QOS, also create the new dedicated bearer id, which is sent back to P-CSCF ?

Any info regarding with is very helpful.

+5 votes
which 3GPP spec has message level details about Sp interface between PCRF and HSS/SPR ?

I have a requirement where I want to fetch User Subscriber Full details at PCRF. Can anyone please tell me about exact 3GPP specification number ?

+3 votes
Handle error scenarios in the PCRF (over Gx interface)

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)

...