摘自规范TS29.210-Charging rule provisioning over Gx。 这部分的介绍是: “The Event-Trigger AVP (AVP code 1006) is of type Enumerated, and it indicates an event that shall cause a re-request of charging rules. The following values are defined: SGSN_CHANGE (0)
This value shall be used to indicate that upon the change of the serving SGSN charging rules shall be requested. QOS_CHANGE (1)
This value shall be used to indicate that upon a QoS change charging rules shall be requested. RAT_CHANGE (2)
This value shall be used to indicate that upon a RAT change charging rules shall be requested. TFT_CHANGE (3)
This value shall be used to indicate that upon a TFT change charging rules shall be requested. PLMN_CHANGE (4)
This value shall be used to indicate that upon a PLMN change charging rules shall be requested.“ Event-Trigger AVP也非常重要,它定义了当某种条件出现后,PCEF或PCRF应重新请求或下发charging rule。目前,规范列出了5种条件。包括用户发生了位置的移动导致服务的SGSN变了、Qos修改了、无线接入类型从2G切换到3G(可能资费标准不一样)、TFT变了(即访问的上层应用发生了变化)、漫游到了其他的PLMN(资费也不一样)等。这些情况产生都需要重新下发charging rule。 如果GGSN上配置了相应的指令,则GGSN会在上述场景出现任意一个时,发送CCR给PCRF请求新的Charging Rule。因此,该AVP应该在CCR消息里出现比较多。当然,PCRF也可以在CCA消息中携带该AVP通知Charging Rule为什么要重新下发的原因。 给出了一个实例截图。
|