Charging-Rule-Definition (The name in message tracing results is charging-rule-definition.)

http://localhost:7904/pages/CEC1230A/01/CEC1230A/01/resources/upcc/maintenance/signaling/figure/fig_cn_90_35_000151_00.png

1003 (Vendor-id = 10415)

Grouped

The syntax of the Charging-Rule-Definition AVP is as follows:

Charging-Rule-Definition ::= < AVP Header: 1003 >

{ Charging-Rule-Name }

[ Service-Identifier ]

[ Rating-Group ]

*[ Flow-Description ]

[ Flow-Status ]

[ QoS-Information ]

[ Reporting-Level ]

[ Online ]

[ Offline ]

[ Metering-Method ]

[ Precedence ]

[ AF-Charging-Identifier ]

*[ Flows ]

[ Redirect-Server ]

[ Proto-Classifier-Name ]

[ X-HW-Monitoring-Key ]

[ Monitoring-Key ]

*[ X-HW-Subscriber-Service-Name ]

[ X-HW-Service-Type ]

[ X-HW-MS-Group-Name ]

[ X-HW-ACL-Group-Name ]

[ X-HW-Interim-Interval ]

*[ Required-Access-Info ]

[ AF-Signalling-Protocol ]

*[ AVP ]

The Charging-Rule-Definition AVP defines the policy and charging control (PCC) rule for a service flow sent by the PCRF to the PCEF. For details about the PCC rule, see PCC Rule.

The Charging-Rule-Definition AVP is also used by the PCRF to instruct the PCEF to install a new dynamic PCC rule or modify a dynamic PCC rule that has been installed.

Certain key sub-AVPs included in the Charging-Rule-Definition AVP are described as follows:

• X-HW-Monitoring-Key: It is added for the usage-based dynamic policy control.

  The X-HW-Monitoring-Key AVP newly added on the PCRF replaces the Rating-Group and Service-Identifier AVPs. It decreases the coupling between the Gx interface and the charging interface, and enhances the flexibility in policy configuration.

  • If the X-HW-Monitoring-Key AVP is not included, the slice is determined by the Rating-Group AVP or the combination of the Rating-Group and Service-Identifier AVPs. The value of the Reporting-Level AVP determines whether the Rating-Group AVP or the combination of the Rating-Group and Service-Identifier AVPs is included.
  • If the X-HW-Monitoring-Key AVP is included, the combination of the Rating-Group and Service-Identifier AVPs become invalid.

• Charging-Rule-Name: It uniquely identifies a PCC rule within one IP-CAN session between the PCRF and the PCEF.

  If a dynamic PCC rule is delivered, its name is dynamically generated by the PCRF and consists of upper case letters. If a predefined PCC rule is delivered, its name must be the same as that defined on the PCEF. Policy case sensitive (VRM_POLICYCASESENSITIVE) is used to determine whether the predefined rule name delivered by the UPCC is case-sensitive.

• Flow-Description: It determines the service flow included in a PCC rule. The Flow-Description AVP must be included in a PCC rule if the PCRF interworks with a Huawei GGSN.

  If any optional AVP within the Charging-Rule-Definition AVP is omitted, but corresponding information has been provided in previous Gx messages, the previous information remains valid. If the Flow-Description AVP is included, it replaces all previous Flow-Description AVPs.

• Flows: It is included only if the AF-Charging-Identifier AVP is included.

For details about how to configure a PCC rule on the UPCC, see Rule.

None.

The Charging-Rule-Definition AVP was first available in RM9000 V300R002C02 and has been enhanced in the following product versions:

• UPCC V300R005C15: The Required-Access-Info and AF-Signalling-Protocol AVPs are added.
• UPCC V300R005C00: Multiple X-HW-Subscriber-Service-Name AVPs are supported.
• UPCC V300R002C06: The Proto-Classifier-Name and X-HW-Subscriber-Service-Name AVPs are added.