CC-Request-Number AVP

Description of AVP

AVP	Description
CC-Request-Number	The CC-Request-Number AVP (AVP Code 415) is of type Unsigned32 and identifies this request within one session. As Session-Id AVPs are globally unique, the combination of Session-Id and CC-Request-Number AVPs is also globally unique and can be used in matching credit-control messages with confirmations. An easy way to produce unique numbers is to set the value to 0 for a credit-control request of type INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the first UPDATE_REQUEST, to 2 for the second, and so on until the value for TERMINATION_REQUEST is one more than for the last UPDATE_REQUEST. NOTE: On the NetEngine 8000 F, the CC-Request-Number AVP identifies the sequence number of the CCR message. The count starts from 0 and the value does not change in retransmitted messages. This AVP is used independently.

AVP

Description

CC-Request-Number

The CC-Request-Number AVP (AVP Code 415) is of type Unsigned32 and identifies this request within one session. As Session-Id AVPs are globally unique, the combination of Session-Id and CC-Request-Number AVPs is also globally unique and can be used in matching credit-control messages with confirmations. An easy way to produce unique numbers is to set the value to 0 for a credit-control request of type INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the first UPDATE_REQUEST, to 2 for the second, and so on until the value for TERMINATION_REQUEST is one more than for the last UPDATE_REQUEST.

NOTE:

On the NetEngine 8000 F, the CC-Request-Number AVP identifies the sequence number of the CCR message.

The count starts from 0 and the value does not change in retransmitted messages.

This AVP is used independently.

Reference Standards

RFC 4006 clause 8.2