This document focuses on Gx interface messages, including CCR/CCA and RAR/RAA messages. This document does not describe capability exchange messages such as the CER/CEA message. For details, see RFC3588.
The mandatory parameters described in this document refer to the mandatory elements in messages. If a mandatory parameter does not exist in messages, the PCRF/PCEF considers the messages to be invalid and service operations cannot be triggered by these messages.
Even if optional parameters do not exist in the messages generated by the PCEF, the PCRF still considers the messages valid. In this case, certain functions may be unavailable but basic procedures are still normal. If optional parameters do not exist in the messages generated by the PCRF, the user does not subscribe to relevant services and the PCEF considers the messages to be valid.
The static rules mentioned in this document are defined by the PCEF. The PCRF can provide instructions on use of one or several static rules by using the Charging-Rule-Name attribute-value pair (AVP) without providing detailed definitions of the rules. The specific Charging-Rule-Name AVP is used only after the PCRF and PCEF complete negotiation.
Dynamic rules are created by users based on the service information and policy configuration on the PCRF. The PCRF allocates a dynamic rule a unique Charging-Rule-Name. During deployment of the policy, the PCRF provides the PCEF with detailed parameters of a rule, for example, QoS parameters and CC-Time. Subsequently, the PCRF can instruct the PCEF to modify or delete the rule by using the Charging-Rule-Name AVP.
Static rules can be activated and deactivated.
Dynamic rules can be deployed, modified, and deleted.
An NetEngine 8000 F receives but does not process *[AVP] in the AVP format description. This means that NetEngine 8000 F processes the attributes described in this document but ignores other redundant attributes.