Event-Trigger AVP

Description of AVP

AVP	Description
Event-Trigger	The Event-Trigger AVP (AVP code 1006) is of type Enumerated. When sent from the PCRF to the PCEF the Event-Trigger AVP indicates an event that shall cause a re-request of PCC rules. When sent from the PCEF to the PCRF the Event-Trigger AVP indicates that the corresponding event has occurred at the gateway. Whenever one of these events occurs, the PCEF shall send the related AVP that has changed together with the event trigger indication. The following values are defined in 3GPP TS 29.212 V9.70: SGSN_CHANGE (0) QOS_CHANGE (1) RAT_CHANGE (2) TFT_CHANGE (3) PLMN_CHANGE (4) LOSS_OF_BEARER (5) RECOVERY_OF_BEARER (6) IP-CAN_CHANGE (7) QOS_CHANGE_EXCEEDING_AUTHORIZATION (11) RAI_CHANGE (12) USER_LOCATION_CHANGE (13) NO_EVENT_TRIGGERS (14) OUT_OF_CREDIT (15) REALLOCATION_OF_CREDIT (16) REVALIDATION_TIMEOUT (17) UE_IP_ADDRESS_ALLOCATE (18) UE_IP_ADDRESS_RELEASE (19) DEFAULT_EPS_BEARER_QOS_CHANGE (20) AN_GW_CHANGE (21) SUCCESSFUL_RESOURCE_ALLOCATION (22) RESOURCE_MODIFICATION_REQUEST (23) PGW_TRACE_CONTROL (24) UE_TIME_ZONE_CHANGE (25) TAI_CHANGE (26) ECGI_CHANGE (27) CHARGING_CORRELATION_EXCHANGE (28) APN-AMBR_MODIFICATION_FAILURE (29) USER_CSG_INFORMATION_CHANGE (30) USAGE_REPORT (33) DEFAULT-EPS-BEARER-QOS_MODIFICATION_FAILURE (34) USER_CSG_HYBRID_SUBSCRIBED_INFORMATION_CHANGE (35) USER_CSG_HYBRID_UNSUBSCRIBED_INFORMATION_CHANGE (36) NOTE: The Event-Trigger AVP is used independently. The following values are supported for the Event-Trigger AVP on the NetEngine 8000 F: LOSS_OF_BEARER_3GPP (5): This value is used in the CCA and RAR messages sent by the PCRF to indicate that the PCEF informs the PCRF of bearer loss. For example, a service is not enabled or a delivered service rule cannot be activated or installed. In this case, the bearer of the service is thought to be lost. The PCEF informs the PCRF of bearer restoration after the service is enabled or the PCRF delivers the service rule. When used in a CCR message, the LOSS_OF_BEARER_3GPP value indicates that the PCEF sends the CCR message because the bearer associated with the PCC rule indicated by the Charging-Rule-Report AVP is lost. In the Charging-Rule-Report AVP, the PCC-Rule-Status AVP should indicate that the PCC rule is temporarily inactive (TEMPORARILY_INACTIVE). RECOVERY_OF_BEARER_3GPP (6): This value is used in the CCA and RAR messages sent by the PCRF to indicate that the gateway informs the PCRF of bearer restoration. When used in a CCR message, the RECOVERY_OF_BEARER_3GPP value indicates that the PCEF sends the CCR message because the bearer associated with the PCC rule indicated by the Charging-Rule-Report AVP is restored. In the Charging-Rule-Report AVP, the PCC-Rule-Status AVP should indicate that the PCC rule becomes active again (ACTIVE). IP_CAN_CHANGE (7): When the access mode of a user changes, the PCEF sends a message carrying the new access mode to request the PCRF to deliver the relevant policy to implement policy control. The policy delivered by the PCRF varies with the user access mode (3GPP/DOCSIS/xDSL/WIMAX/3GPP2). The IP_CAN_CHANGE trigger must be configured when policy control is implemented based on access mode. USAGE_REPORT (33): When the PCRF sends the quota through the Usage-Monitoring-Information AVP (including the Monitoring-Key AVP and the Granted-Service-Unit AVP) in a CCA or RAR message, the PCRF must also send the Event-Trigger of USAGE_REPORT. When the PCEF reports usage through the Usage-Monitoring-Information AVP (including the Monitoring-Key AVP and the Used-Service-Unit AVP) in a CCR message, the PCEF must send the Event-Trigger of USAGE_REPORT to implement policy control based on the status of accounts or the quotas. NOTE: NetEngine 8000 F can identify USAGE_REPORT(26) by default. After receiving an Event-Trigger AVP with a value of 33, NetEngine 8000 F does not process it.

AVP

Description

Event-Trigger

The Event-Trigger AVP (AVP code 1006) is of type Enumerated. When sent from the PCRF to the PCEF the Event-Trigger AVP indicates an event that shall cause a re-request of PCC rules. When sent from the PCEF to the PCRF the Event-Trigger AVP indicates that the corresponding event has occurred at the gateway. Whenever one of these events occurs, the PCEF shall send the related AVP that has changed together with the event trigger indication.

The following values are defined in 3GPP TS 29.212 V9.70:

SGSN_CHANGE (0)
QOS_CHANGE (1)
RAT_CHANGE (2)
TFT_CHANGE (3)
PLMN_CHANGE (4)
LOSS_OF_BEARER (5)
RECOVERY_OF_BEARER (6)
IP-CAN_CHANGE (7)
QOS_CHANGE_EXCEEDING_AUTHORIZATION (11)
RAI_CHANGE (12)
USER_LOCATION_CHANGE (13)
NO_EVENT_TRIGGERS (14)
OUT_OF_CREDIT (15)
REALLOCATION_OF_CREDIT (16)
REVALIDATION_TIMEOUT (17)
UE_IP_ADDRESS_ALLOCATE (18)
UE_IP_ADDRESS_RELEASE (19)
DEFAULT_EPS_BEARER_QOS_CHANGE (20)
AN_GW_CHANGE (21)
SUCCESSFUL_RESOURCE_ALLOCATION (22)
RESOURCE_MODIFICATION_REQUEST (23)
PGW_TRACE_CONTROL (24)
UE_TIME_ZONE_CHANGE (25)
TAI_CHANGE (26)
ECGI_CHANGE (27)
CHARGING_CORRELATION_EXCHANGE (28)
APN-AMBR_MODIFICATION_FAILURE (29)
USER_CSG_INFORMATION_CHANGE (30)
USAGE_REPORT (33)
DEFAULT-EPS-BEARER-QOS_MODIFICATION_FAILURE (34)
USER_CSG_HYBRID_SUBSCRIBED_INFORMATION_CHANGE (35)
USER_CSG_HYBRID_UNSUBSCRIBED_INFORMATION_CHANGE (36)

NOTE:

The Event-Trigger AVP is used independently.

The following values are supported for the Event-Trigger AVP on the NetEngine 8000 F:

LOSS_OF_BEARER_3GPP (5): This value is used in the CCA and RAR messages sent by the PCRF to indicate that the PCEF informs the PCRF of bearer loss. For example, a service is not enabled or a delivered service rule cannot be activated or installed. In this case, the bearer of the service is thought to be lost. The PCEF informs the PCRF of bearer restoration after the service is enabled or the PCRF delivers the service rule. When used in a CCR message, the LOSS_OF_BEARER_3GPP value indicates that the PCEF sends the CCR message because the bearer associated with the PCC rule indicated by the Charging-Rule-Report AVP is lost. In the Charging-Rule-Report AVP, the PCC-Rule-Status AVP should indicate that the PCC rule is temporarily inactive (TEMPORARILY_INACTIVE).
RECOVERY_OF_BEARER_3GPP (6): This value is used in the CCA and RAR messages sent by the PCRF to indicate that the gateway informs the PCRF of bearer restoration. When used in a CCR message, the RECOVERY_OF_BEARER_3GPP value indicates that the PCEF sends the CCR message because the bearer associated with the PCC rule indicated by the Charging-Rule-Report AVP is restored. In the Charging-Rule-Report AVP, the PCC-Rule-Status AVP should indicate that the PCC rule becomes active again (ACTIVE).
IP_CAN_CHANGE (7): When the access mode of a user changes, the PCEF sends a message carrying the new access mode to request the PCRF to deliver the relevant policy to implement policy control. The policy delivered by the PCRF varies with the user access mode (3GPP/DOCSIS/xDSL/WIMAX/3GPP2). The IP_CAN_CHANGE trigger must be configured when policy control is implemented based on access mode.
USAGE_REPORT (33): When the PCRF sends the quota through the Usage-Monitoring-Information AVP (including the Monitoring-Key AVP and the Granted-Service-Unit AVP) in a CCA or RAR message, the PCRF must also send the Event-Trigger of USAGE_REPORT. When the PCEF reports usage through the Usage-Monitoring-Information AVP (including the Monitoring-Key AVP and the Used-Service-Unit AVP) in a CCR message, the PCEF must send the Event-Trigger of USAGE_REPORT to implement policy control based on the status of accounts or the quotas.

NOTE:
NetEngine 8000 F can identify USAGE_REPORT(26) by default. After receiving an Event-Trigger AVP with a value of 33, NetEngine 8000 F does not process it.

Reference Standards

3GPP TS 29.212 V9.7.0 clause 5.3.7