top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Why do we require Capabilities Update Procedure (DIAMETER) ?

+2 votes
510 views

What is the sense of giving Capabilities Update Procedure described in new RFC-6737.

posted Apr 25, 2014 by Atif

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

1 Answer

+5 votes

Before Capabilities Update Procedure (CUR/CUA) there was only CER/CEA.
When we are starting a connection CER/CEA exchange will happen.

After that if the application has upgraded/updated then to made the changes to other Peers we must bring down the application and again CER/CEA will happen.

We have to restart the connection so obvious the outage will be there for some time (restarting time).

In similar way When we want to upgrade/update the application in open state this CUR/CUA will be required to prevent those outage time. With these the upgradation will be easy.

This is the main reason for CUR/CUA procedures.

answer Apr 28, 2014 by Hiteshwar Thakur
Similar Questions
+2 votes
How these Capabilities Update Procedure Works ?

I had a look on this Q/A and got one thing in my mind. How this Procedure works ? because i have read the both RFC but did not find this Procedure and there working.

Reference: http://tech.queryhome.com/41739/why-do-we-require-capabilities-update-procedure-diameter

+2 votes
Getting RST from diameter after Capabilities-Exchange-Answer

We are connecting the PCEF to PCRF. But the Gx link is not coming up. I have observed that there are CER/CEA successful between PCEF a PCRF. DWR is generated by PCRF (i.e. seen in the logs) but it is not sent (i.e. not seen in the capture). Any suggestion on what could be the issue.

+2 votes
LTE: Why does the MME execute Update Location Procedure towards HSS ?

In what all scenarios, this procedure gets executed ? And why this procedure need to be executed ?

+2 votes
Diameter LTE Location Update

Hello LTE n/w experts,

I have a Query regarding the UpdateLocation Diamter message. I have a issue in the legacy code, where the AVP "Supported-Features" which is optional is not handled. Now when we are testing with different vendor PGW, we are getting the following AVPS
AVP format

 Supported-Features ::=  < AVP Header: 628 10415 >
                         { Vendor-Id (AVP code 266)}
                         { Feature-List-ID (629)}
                         { Feature-List (630)}
                        *[ AVP ]

AVP format

MIP6-Agent-Info ::=  < AVP Header: 486 >
                    *2[ MIP-Home-Agent-Address (334)]
                      [ MIP-Home-Agent-Host (348)]
                      [ MIP6-Home-Link-Prefix (125)]
                     *[ AVP ]
  MIP6-Agent-Info ::=  < AVP Header: 486 >
                    *2[ MIP-Home-Agent-Address (334)]
                      [ MIP-Home-Agent-Host (348)]
                      [ MIP6-Home-Link-Prefix (125)]
                     *[ AVP ]

I am not sure why the Location Update has these new IEs. I am new to network side. So any help in this regard will be greatly appreciated.

...