top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What Origin-State-Id AVP signifies with the value "0" ?

+2 votes

Can someone please explain, what is the significance of "0" and non"0" value of Origin-State-Id AVP in a diameter message ?

posted Dec 21, 2014 by Vikram Singh

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

3 Answers

+2 votes

When Origin-State Id is set to 0, in that case the node signifies that it will not support the intimation of restart of that node. However if that value is set to a non zero value in that case it signifies that it supports such feature.

The value communicated during the CER if incremented due to the restart of the diameter node in any subsequent intimates the other node that the node has been restared and it can clear the session created previously.

answer Dec 21, 2014 by Peeyush Sharma
+2 votes

On behalf of Bart -

Value of this avp tells if the state of peer has changed or not. It could be due to connection/session break or in case the peer was rebooted.

Value is incremented, to tell the far end that all of the connections/sessions are no longer valid.

Hope this helps

answer Dec 22, 2014 by Salil Agrawal
0 votes

Just adding specific info from the RFC 3588 sec 8.

When a Diameter server receives an Origin-State-Id that is greater
than the Origin-State-Id previously received from the same issuer, it
may assume that the issuer has lost state since the previous message
and that all sessions that were active under the lower Origin-State-
Id have been terminated. The Diameter server MAY clean up all
session state associated with such lost sessions, and MAY also issues
STRs for all such lost sessions that were authorized on upstream
servers, to allow session state to be cleaned up globally.

The Origin-State-Id AVP also present in Device-Watchdog Answer sent in response to Device-Watchdog Request.

If the value is ZERO means no reboot happened or u can say no restart happened.

answer Oct 22, 2016 by Sanjeet Singh
Similar Questions
+3 votes

I have a query regarding usage of Origin-State-Id AVP in Diameter. The Diameter Base Protocol RFC 3588 says that Origin-State-Id AVP MAY be included in any diameter message.

Now, some diameter based application (like a 3GPP defined application) defines new commands and in those commands’ ABNF Origin-State-Id AVP is not present.

Then does this imply that Origin-State-Id AVP MUST not be sent in these commands or it can be sent because RFC 3588 says it can be sent in any diameter message?

+3 votes

I found 1 * [vendor-id] as a single AVP in rfc3588. Can someone please explain means of 1 * [AVP] ?

+5 votes

I gone through the RFC4006 but didnt get the context of below paragraph

   Certain applications require multiple credit-control sub-sessions.
   These applications would send messages with a constant Session-Id
   AVP, but with a different CC-Sub-Session-Id AVP.  If several credit
   sub-sessions will be used, all sub-sessions MUST be closed separately
   before the main session is closed so that units per sub-session may
   be reported.  The absence of this AVP implies that no sub-sessions
   are in use.

But here my question is
1. What could be the types of Multiple credit-ontrol Sub-session?
2. How can we include different cc-sub-session-ID for each sub-session, please give me an example with message structure using CCR message.

0 votes

When a ULR includes AVP 1493 Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions = NOT-SUPPORTED(0), does it mean that it is a regular LTE registration or it can end with VoLTE registration?

+5 votes

Also what are the rules for populating those AVPs (in the RFC it is not clear when to use each one of the option)?