top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

What is the DEA and how it is different then DRA?

+2 votes
886 views

While answering a question I suggested use of DEA but back in the mind I tried to find what is DEA and how it is different from DRA.

posted Mar 9, 2015 by Salil Agrawal

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

1 Answer

0 votes

On behalf of Bart
How I see it the DEA is secured DRA.

In previous post I referred to DRA just after the FW, used to hide topology from other VPLMNs.
Instead of involving the security team and ask them to fitler out something on the FW, and then ask DRA to remove unwanted AVPs, you could put this on DEA.

answer Mar 9, 2015 by Salil Agrawal
Can you expound the answer a bit?
The DEA functionality is used for roaming purpose.It is implemented at nw edge thats why it is called Diameter Edge Agent.In this mode it implements the topology hiding features between Operator 1 and Operator 2 nw for roaming scenerios
Similar Questions
+2 votes

3GPP TS 29.272 says in section 7.1.6/ Routing considerations the following sentence:
If an MME or SGSN knows the address/name of the HSS for a certain user, and the associated home network domain name, both the Destination-Realm and Destination-Host AVPs shall be present in the request......

In Diameter Base Protocol RFC 6733 you can read the following :
6.1.4. Processing Local Requests
A request is known to be for local consumption when one of the following conditions occurs:
o The Destination-Host AVP contains the local host’s identity;
o The Destination-Host AVP is not present, the Destination-Realm AVP contains a realm the server is configured to process locally, and the Diameter application is locally supported; or
o Both the Destination-Host and the Destination-Realm are not present.

Following erroneous Scenario:
1) The MME sends a Request to the Destination Host e.g. HSS_ABC01.xxx via the DRA. The Request contains Destination-Host and Destination-Realm…
2) But what happens when this HSS_ABC01.xxx is unavailable (out of order)? Would the DRA send/forward the Request from MME to a second HSS (front end)?, e.g. hssDEF01.xxx?
3) Would the 2nd HSS Frontend “hssDEF01.xxx” complain that the Destination Host does not match as DRA sent to 2nd HSS frontend the Request with Destination-Host = HSS_ABC01.xxx
-->should the DRA be smarter when the 1st HSS Frontend is unavailable ? my question is what can DRA do in such case when the original destination is out of order?

FYI:
DIAMETER_UNABLE_TO_DELIVER 3002
This error is given when Diameter cannot deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request or because the Destination-Host AVP was given without the associated Destination-Realm AVP.

0 votes

In case there is a DRA between PGW and PCRF, then what should ideally be sent in the Destination-Host AVP in the CCR-Initial messsage?Do we send the Destination-Host name for the final destination of the PCRF or is it the next hop peer ; which is the DRA in this case?

+2 votes

As per my understanding DRA is must to connect MME to multiple HSSs.

My question is: is there any considerations for connecting number of HSS's to MME without DRA, or its just a must to have DRA for connecting HSS's at VPLMN's?

+3 votes

For example it can be used in the HSS mnc.ncc.3gppnetwork.org and in the MME mnc.ncc.3gpp.org. Or must be same mnc.ncc.3gppnetwork.org?

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...