Blocking Data usage using Diameter Rx to the PCRF

359 views

Is it possible to block all Data traffic for a specific UE by sending Diameter-Rx AAR command to the PCRF?
If yes, can you indicate AVPs shall be present in the AAR?
May I suppose the following AVP list
- Subscription-Id Containing the targeted MSISDN/IMSI
- Framed-IP-Address or Framed-IPv6-Prefix (containing the IP-address allocated to the UE)
- Media-Component-description containing the following Sub AVP
- Media-Component-number Mandatory sub-AVP
- Flow-Status set to DISABLED

posted Jun 5, 2018 by Michael Semama

Looking for an answer? Promote on:

Facebook Share Button

Twitter Share Button

LinkedIn Share Button

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.

+4 votes

PCRF Rx AAR message related Query

Hello,

I have been able to write a standalone basic PCRF code in our software.

I had also written them using the Gx and RX interfaces (i.e using the diameter protocol). There was no time to test this feature.

Now I find flaws in my design regarding the Diameter while testing.

Initially the SIP (i.e ike IMS) was sending the request to PGW to create the voice bearer. Now my initial implemetation of Rx i thought the TFT was calculated in the SIP and sent across in the RX, but now when revisiting the code, i feel, that there was no such parameter to pass this info to the PCRF from SIP.

Now my doubt is, how this info related to TFT is being passed across to PCRF. Is it through the "Flows".
If so how to get the TFT in the PCRF to send back to PGW...I have missed this part of the design as i was looking more into the QOS..

Any help is greatly appreciated.

thanks
pdk

+2 votes

Policy counter subscription by the PCRF to OCS

Hi,

I am going through the spec 3gpp 29.219(Sy interface) and trying to understand the call flow and AVPS between the OCS and PCRF.

The PCRF sends the the list of Policy counters to OCS initially and OCS will store it against the Sy session. How does the Counter identifiers be identified uniquely b.w OCS and PCRF ?

Because the spec says, If the OCS determines that any policy counter identifiers are invalid, the OCS shall return a response with the Result-Code AVP set to DIAMETER_INVALID_AVP_VALUE.

But my doubt is, how the Policy counter Ids are known across the OCS and PCRF.

Any help in this area is very helpful

Thanks

+1 vote

RESOURCES_LIMITATION failure code sent by SAE-GW on Rx?

I would like to understand that under what circumstances the “ RESOURCES_LIMITATION” failure code sent by SAE-GW on Rx?

0 votes

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

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 ?

...