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

Facebook Login
Site Registration

DIAMETER: How does a node support multiple diameter applications ?

+1 vote

I have a very generic question. I took PCEF to describe my problem.
PGW supports multiple diameter based applications like Gx, Gy and Gz. When a message receives at PCEF from the peer diameter entities, how does PCEF come to know source of message and after that what PCEF does to forward this message to the proper application running at the PCEF.

My question is implementation specific. Please provide inputs in details.

I also want to know about session termination in Diameter protocol. Again, I am considering PCEF to describe my question. When a session is established between PCEF and PCRF ? either (CER and CEA) or (CCR and CCA) ?

posted Mar 22, 2014 by Vimal Kumar Mishra

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

2 Answers

0 votes

As to generic question.
You have to go and read about realms and peers in Diameter.
Based on my hands-on experience, the Gy and Gx/Gz were always from different realms - this is how PCEF know where form he got the message.
Everyone please correct my if I'm wrong or give your inputs.

As to the CCR-I and CCA-I you have to go back to the basic attach procedure. You can find this on my blog here

answer Mar 23, 2014 by Bart Barton
0 votes

Not sure if I understood the question correctly -

Just check the CCR message

<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY >
                                   < Session-Id >
                                   { Origin-Host }
                                   { Origin-Realm }
                                   { Destination-Realm }
                                   { Auth-Application-Id }
                                   { Service-Context-Id }
                                   { CC-Request-Type }
                                   { CC-Request-Number }
                                   [ Destination-Host ]
                                   [ User-Name ]
                                   [ CC-Sub-Session-Id ]
                                   [ Acct-Multi-Session-Id ]
                                   [ Origin-State-Id ]
                                   [ Event-Timestamp ]
                                  *[ Subscription-Id ]
                                   [ Service-Identifier ]
                                   [ Termination-Cause ]
                                   [ Requested-Service-Unit ]
                                   [ Requested-Action ]
                                  *[ Used-Service-Unit ]
                                   [ Multiple-Services-Indicator ]
                                  *[ Multiple-Services-Credit-Control ]
                                  *[ Service-Parameter-Info ]
                                   [ CC-Correlation-Id ]
                                   [ User-Equipment-Info ]
                                  *[ Proxy-Info ]
                                  *[ Route-Record ]
                                  *[ AVP ] 

Which contains the application-id (the same is already negotiated in CER/CEA) which can be used by the PCEF or any other node which is supporting diameter.

Subsequent diameter message in the case of stateless scenarios may not contain the app-id but the same thing diameter can retrieve from session context.

Coming to your second question, session termination is done via the STR.

answer Mar 23, 2014 by Salil Agrawal
Similar Questions
+4 votes

I am not able to understand the significance of "limited success" in a answer message and also want to know what a diameter node does when it receives this limited success within a answer message ?

0 votes

I know Diameter client can re-transmit the request message until it receives the answer message.
But what about when a Diameter node has sent answer message to the last received request from its peer and that's is not received but its peer. In this case, from Diameter client node transaction is not completed since it did not receive answer message but from other node point of view it has responded with answer and transaction is completed.

+3 votes

Is there any standard way to create and maintain the peer table ?

0 votes

In one Diameter blog, I saw a statement in which mentioned, if a Diameter node receive CER from unknown peer it responds back to that peer with Result-Code AVP set to "DIAMETER_UNKNOWN_PEER".
Now my query, Does a Diameter node keep its potential peers information in advance ?

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.