Origin-State-Id

Description of AVP

AVP	Description
Origin-State-Id	The Origin-State-Id AVP (AVP Code 278) is of type Unsigned32 and the length is 4 bytes. The Origin-State-Id AVP is a monotonically increasing value that is used whenever a Diameter entity restarts with the loss of a previous status, for example upon reboot. The Origin-State-Id AVP can be carried in any Diameter message, including CER. Typically, Origin-State-Id is used by an access device that always starts up with no active sessions; that is, any session that is active before the restart will be lost. By carrying the Origin-State-Id AVP in a message, it allows other Diameter entities to infer that sessions associated with a lower Origin-State-Id are no longer active. If an access device does not intend for such inferences, the device must include the Origin-State-Id AVP in any message or set its value to 0. NOTICE: The NetEngine 8000 F can receives but does not process the Origin-State-Id AVP.

AVP

Description

Origin-State-Id

The Origin-State-Id AVP (AVP Code 278) is of type Unsigned32 and the length is 4 bytes. The Origin-State-Id AVP is a monotonically increasing value that is used whenever a Diameter entity restarts with the loss of a previous status, for example upon reboot. The Origin-State-Id AVP can be carried in any Diameter message, including CER. Typically, Origin-State-Id is used by an access device that always starts up with no active sessions; that is, any session that is active before the restart will be lost. By carrying the Origin-State-Id AVP in a message, it allows other Diameter entities to infer that sessions associated with a lower Origin-State-Id are no longer active. If an access device does not intend for such inferences, the device must include the Origin-State-Id AVP in any message or set its value to 0.

NOTICE:

The NetEngine 8000 F can receives but does not process the Origin-State-Id AVP.

Reference Standards

RFC 3588 clause 8.16