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

Facebook Login
Site Registration

DIAMETER: What does the difference between Result-Code and Experimental-Result-Code AVPs ?

+6 votes
1,224 views

Can someone please explain difference between these two. Could both Result-Code and Experimental-Result AVPs be used in same diameter or only one of them is allowed ?

posted Mar 7, 2014 by Harshita

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

3 Answers

+1 vote
  • I think Experimental Result code AVP is for Vendor Specific error codes.

  • Experimental Result is an group AVP which contains two AVP's inside it:

    1. Vendor Id
    2. Experimental Result Code

Yes, in one diameter message both can be present

answer Mar 10, 2014 by Hiteshwar Thakur
Can you please share any reference which tells that result-code AVP and experimental-result code avp both can be part of a diameter message.
Thanks in advance.
In any diameter message both AVP cannot be present at the same time.

Experimental Result Codes are used for permanent failures.
+1 vote
  • The result codes are unified and predefined in RFC3588.
    These typically don't cover any application level error (e.g. Unknown_user).
  • The meaning of values of Experimental result codes can vary according to the included Vendor-ID AVP.
    There are 3GPP standard values (Vendor-id="3GPP"=10415), defined in TS 29.229, but another set of values might be used, provided by another vendor.
  • The RFC above writes:

All Diameter answer messages *defined in vendor-specific
applications* must include either one Result-Code AVP or one
Experimental-Result AVP.

answer Mar 26, 2015 by Berci Pécsi
+1 vote

In Diameter, Result Codes are some thing which will give u the Result of the Operation at Diameter Level.. For EX: 2001 is Diameter_Success..

Result Codes have Negative or Error Responses along with Positive Responses..

Where are EXPERIMENTAL_RESULT_CODES give the Application Level Failures..

Result Codes Errors are typically protocol or Base level Errors Where are EXP RESULT CODES gives specific Information about Application Level Failures

answer Dec 1, 2016 by Rohit Maruthi Sesha Sairam Vullaganti
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 ?

+3 votes

I'm doing some integration toward Gy client (PCEF), and encountered an unclear area. I'm not sure if it is unclear in RFC 4006 or the 3GPP TS32.299 or both.

Scenario: A user logs on. The user has no credit left for a rating-group 42.

CCR-initial and CCA-initial:
Nothing interesting. In Gy it is typically just "empty" requests for the purpose of registering the user session.

The user then attempts to use rating-group 32:

CCR-update:

 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Requested-Service-Unit {
 }
 }

to which the OCS (Gy server) would normally respond:

CCA-update:

 Result-Code = 2001 (success)
 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Result-Code = 4012 (credit-limit-reached)
 Final-Unit-Indication {
 ...
 }
 }

However, the Gy specification says that a zero-grant is needed, which to me sounds a bit odd, but nevertheless:

Result-Code = 2001 (success)
 Multiple-Services-Credit-Control {
 Rating-Group = 42
 Result-Code = 4012 (credit-limit-reached)
 Granted-Service-Unit {
 CC-Total-Octets = 0
 }
 Final-Unit-Indication {
 ...
 }
 }

Now, the Gy client vendor says that the result-code inside the MSCC must be 2001 (success). It sort of makes sense because there is a grant.

But that made me wonder: In which case would result-code=4012 make sense? Is it just 3GPP who has "mangled" diameter-credit-control in the Gy application?

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
...