top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Which specification need to refer for Rx interface ?

+2 votes
344 views
Which specification need to refer for Rx interface ?
posted Sep 22, 2014 by Harshita

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

1 Answer

+1 vote

TS 29.214 for Rx interface

http://www.3gpp.org/DynaReport/29214.htm

answer Sep 24, 2014 by Peeyush Sharma
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.

+2 votes
Blocking Data usage using Diameter Rx to the PCRF

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

+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?

...