Session-Release-Cause AVP

Description of AVP

AVP	Description
Session-Release-Cause	The Session-Release-Cause AVP (AVP Code 1045) is of type Enumerated and it determines the reason of the IP-CAN session released by the PCRF. The following values are defined for the Session-Release-Cause AVP: UNSPECIFIED_REASON (0) This value is used for unspecified reasons. UE_SUBSCRIPTION_REASON (1) This value is used to indicate that the UE subscription data has changed (for example, subscription data was deleted) and a session needs to be terminated. INSUFFICIENT_SERVER_RESOURCES (2) This value is used to indicate that the server is overloaded and a session needs to be terminated. UE_SUBSCRIPTION_REASON (1) NOTICE: For the release of an IP-CAN session initiated by the PCRF, 3GPP defines three different mechanisms successively. The first mechanism is based on Diameter based protocol (DBP) ASR/ASA messages; the second mechanism is based on the RAR messages (in which all deployed rules are removed) sent by the PCRF; the third mechanism is based on the RAR messages (carrying the Session-Release-Cause AVP) sent by the PCRF. The PCEF removes the deployed policies and sends a CCR-T message to the PCRF, requesting the PCRF to terminate an IP-CAN session. From the angle of interoperability and compatibility, the third mechanism is mandatory and the other two are optional.

AVP

Description

Session-Release-Cause

The Session-Release-Cause AVP (AVP Code 1045) is of type Enumerated and it determines the reason of the IP-CAN session released by the PCRF.

The following values are defined for the Session-Release-Cause AVP:

UNSPECIFIED_REASON (0)

This value is used for unspecified reasons.
UE_SUBSCRIPTION_REASON (1)

This value is used to indicate that the UE subscription data has changed (for example, subscription data was deleted) and a session needs to be terminated.
INSUFFICIENT_SERVER_RESOURCES (2)

This value is used to indicate that the server is overloaded and a session needs to be terminated.

UE_SUBSCRIPTION_REASON (1)

NOTICE:

For the release of an IP-CAN session initiated by the PCRF, 3GPP defines three different mechanisms successively. The first mechanism is based on Diameter based protocol (DBP) ASR/ASA messages; the second mechanism is based on the RAR messages (in which all deployed rules are removed) sent by the PCRF; the third mechanism is based on the RAR messages (carrying the Session-Release-Cause AVP) sent by the PCRF. The PCEF removes the deployed policies and sends a CCR-T message to the PCRF, requesting the PCRF to terminate an IP-CAN session. From the angle of interoperability and compatibility, the third mechanism is mandatory and the other two are optional.

Reference Standards

3GPP TS 29.212 V9.7.0 clause 5.3.44