CC-Request-Type AVP

Description of AVP

AVP	Description
CC-Request-Type	The CC-Request-Type AVP (AVP Code 416) is of type Enumerated and contains the reason for sending the credit-control request message. It must be present in all Credit-Control-Request messages. The following values are defined for the CC-Request-Type AVP: INITIAL_REQUEST(1) An Initial request is used to initiate a credit-control session, and contains credit control information relevant to the initiation. UPDATE_REQUEST(2) An Update request contains information about an existing credit-control session. An Update credit-control request needs to be sent each time a credit-control re-authorization is required at the expiry of the allocated quotas or validity time. In addition, additional service-specific events may trigger an Update request. TERMINATION_REQUEST(3) A termination request is sent to terminate a credit-control session and contains credit-control information relevant to the existing session. EVENT_REQUEST(4) An event request is used when there is no need to maintain any credit-control session status in the credit-control server. This request contains all information relevant to the service, and can be only used for a service request. The reason for the Event request is further detailed in the Requested-Action AVP. The Requested-Action AVP must be carried in Credit-Control-Request messages when CC-Request-Type is set to EVENT_REQUEST. NOTE: This AVP is used independently. Currently, the NetEngine 8000 F supports the following types of CC requests: INITIAL_REQUEST(1) UPDATE_REQUEST(2) TERMINATION_REQUEST(3)

AVP

Description

CC-Request-Type

The CC-Request-Type AVP (AVP Code 416) is of type Enumerated and contains the reason for sending the credit-control request message. It must be present in all Credit-Control-Request messages. The following values are defined for the CC-Request-Type AVP:

INITIAL_REQUEST(1)

An Initial request is used to initiate a credit-control session, and contains credit control information relevant to the initiation.
UPDATE_REQUEST(2)

An Update request contains information about an existing credit-control session. An Update credit-control request needs to be sent each time a credit-control re-authorization is required at the expiry of the allocated quotas or validity time. In addition, additional service-specific events may trigger an Update request.
TERMINATION_REQUEST(3)

A termination request is sent to terminate a credit-control session and contains credit-control information relevant to the existing session.
EVENT_REQUEST(4)

An event request is used when there is no need to maintain any credit-control session status in the credit-control server. This request contains all information relevant to the service, and can be only used for a service request. The reason for the Event request is further detailed in the Requested-Action AVP. The Requested-Action AVP must be carried in Credit-Control-Request messages when CC-Request-Type is set to EVENT_REQUEST.

NOTE:

This AVP is used independently.

Currently, the NetEngine 8000 F supports the following types of CC requests:

INITIAL_REQUEST(1)
UPDATE_REQUEST(2)
TERMINATION_REQUEST(3)

Reference Standards

RFC 4006 clause 8.3