The Credit Control Request (CCR) command, indicated by the Command-Code field set to 272 and the R bit set in the Command Flags field, is sent by the PCEF to the PCRF in order to request PCC rules. The CCR command is also sent by the PCEF to the PCRF in order to indicate PCC rule related events or the termination of the IP CAN session.
CCR-Initial: Upon receiving an IP-CAN session establishment request message (for example, request for Internet access), the PCEF sends an IP-CAN session authorization request message to the PCRF. Based on the IP-CAN session authorization request message, the PCRF generates a charging control policy.
An IP CAN session is being established, modified, or terminated.
UE resources change.
An event is triggered.
CCR-Terminate: After receiving a request for going offline from a user, the PCEF must terminate the IP-CAN session. The PCEF sends an IP session termination authorization request message (a CCR message) to the PCRF to instruct the PCRF to release the related policy.
<CC-Request> ::= < Diameter Header: 272, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ CC-Request-Type } [Note1]
{ CC-Request-Number } [Note2]
[ Supported-Features ]
{ Vendor-Id }
{ Feature-List-ID }
{ Feature-List }
*[ Subscription-Id ] [Note3]
{ Subscription-Id-Type }
{ Subscription-Id-Data }
[ Framed-IP-Address ] [Note4]
[ Framed-IPv6-Prefix ] [Note5]
[ IP-CAN-Type ] [Note6]
[ User-Equipment-Info ] [Note7]
{ User-Equipment-Info-Type }
{ User-Equipment-Info-Value }
[ X-HW-User-Physical-Info-Value ] [Note8]
[ QoS-Information ] [Note9]
[ Max-Requested-Bandwidth-UL ]
[ Max-Requested-Bandwidth-DL ]
[ Guaranteed-Bitrate-UL ]
[ Guaranteed-Bitrate-DL ]
Note Index |
Note Description |
|---|---|
[Note1] |
In the IP-CAN session authorization establishment request message, the value of CC-Request-Type is INITIAL_REQUEST. |
[Note2] |
The CC-Request-Number AVP is used to distinguish requests or responses in a session because a Session-Id is globally unique. The value of this AVP is set to 0 when a session is established. |
[Note3] |
A CCR-Initial message must carry the Subscription-Id AVP; otherwise, a failure will occur. This AVP consists of the Subscription-Id-Type AVP and the Subscription-Id-Data AVP. For NetEngine 8000 F, the Subscription-Id-Type AVP is set to END_USER_NAI. The Subscription-Id-Data AVP is set to a user name consisting of a maximum of 253 bytes (for example, 206c6d2d0000@rm-1). |
[Note4] |
An IP-CAN session authorization request message must include the Framed-IP-Address AVP or Framed-IPv6-Prefix AVP (specifically, it must contain a user address). Otherwise, the message is considered invalid. If a request message carries both of the preceding AVPs, the PCRF uses an IPv4 address as the user address. |
[Note5] |
Either an IPv6 address or the Frame-IP-Address AVP must exist. |
[Note6] |
The IP-CAN-Type AVP indicates the type of the access network to which users are connected for PCRF management. The value of IP-CAN-Type of the NetEngine 8000 F V800R021C00SPC100 is permanently set to XDSL(2). For other values, see related AVP descriptions. |
[Note7] |
The User-Equipment-Info AVP is used to report user equipment information (user MAC addresses). The AVP consists of User-Equipment-Info-Type AVP and User-Equipment-Info-Value AVP. For the NetEngine 8000 F V800R021C00SPC100, the received AVP is not processed. |
[Note8] |
The X-HW-User-Physical-Info-Value AVP is a private AVP. It is used to report physical information of a user, such as slot ID, sub-slot ID, port ID, and VLANID. The format of the X-HW-User-Physical-Info-Value AVP is similar to that of the RADIUS NAS-PORT-ID AVP and is set to a maximum of 65 bytes. An example of the X-HW-User-Physical-Info-Value AVP is: {atm|eth|trunk} NAS_slot/NAS_subslot/NAS_port:XPI.XCI. |
<CC-Request> ::= < Diameter Header: 272, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ CC-Request-Type } [ Note 1 ]
{ CC-Request-Number } [ Note 2 ]
[ Subscription-Id ] [ Note 3 ]
{ Subscription-Id-Type }
{ Subscription-Id-Data }
[ Framed-IP-Address ] [ Note 4 ]
[ Framed-IPv6-Prefix ] [ Note 5 ]
[ IP-CAN-Type ] [ Note 6 ]
[ User-Equipment-Info ] [ Note 7 ]
{ User-Equipment-Info-Type }
{ User-Equipment-Info-Value }
*[ Charging-Rule-Report ]
*[ Charging-Rule-Name ]
[ PCC-Rule-Status ]
[ Rule-Failure-Code ]
[ X-HW-User-Physical-Info-Value ] [ Note 8 ]
*[ Event-Trigger ] [ Note 9 ]
*[ Usage-Monitoring-Information ] [ Note 10 ]
[ Monitoring-Key ]
[ Usage-Monitoring-Level ]
[ Used-Service-Unit ]
[ CC-Time ]
[ CC-Total-Octets ]
[ Usage-Monitoring-Report ]
[ CC-Time ]
[ CC-Total-Octets ]
[ Usage-Monitoring-Report ]
[ Usage-Monitoring-Support ]
Note Index |
Note Description |
|---|---|
[Note1] |
In the IP-CAN session authorization modification request message, the value of CC-Request-Type is UPDATE_REQUEST. |
[Note2] |
The CC-Request-Number AVP is used to distinguish requests or responses in a session because a Session-Id is globally unique. The value of CC-Request-Number increases by 1 each time a session is modified. |
[Note3] |
The Subscription-Id AVP consists of the Subscriber-Id-Type AVP and Subscription-Id-Data AVP. |
[Note4] |
An IP-CAN session authorization request message must include the Framed-IP-Address AVP or Framed-IPv6-Prefix AVP (specifically, it must contain a user address). Otherwise, the message is considered invalid. If a request message carries both of the preceding AVPs, the PCRF uses an IPv4 address as the user address. |
[Note5] |
Either an IPv6 address or the Frame-IP-Address AVP must exist. |
[Note6] |
The IP-CAN-Type AVP indicates the type of the access network to which users are connected for PCRF management. The value of IP-CAN-Type of the NetEngine 8000 F is permanently set to XDSL(2). For other values, see related AVP descriptions. |
[Note7] |
The User-Equipment-Info AVP is used to report user equipment information (user MAC addresses). This AVP consists of the User-Equipment-Info-Type AVP and the User-Equipment-Info-Value AVP. |
[Note8] |
X-HW-User-Physical-Info-Value is a private AVP. It is used to report physical information of a user, such as slot ID, sub-slot ID, port ID, and VLANID. The format of the X-HW-User-Physical-Info-Value AVP is similar to that of the RADIUS NAS-PORT-ID AVP and is set to a maximum of 65 bytes. An example of the X-HW-User-Physical-Info-Value AVP is: {atm|eth|trunk} NAS_slot/NAS_subslot/NAS_port:XPI.XCI. |
[Note9] |
The PCEF sends to the PCRF an Event-Trigger AVP to indicate the occurrence of an event on the gateway. While the event is ongoing, the PCEF sends the affected AVPs in addition to the Event-Trigger AVP. For the value range, see the related AVP definition. |
[Note10] |
The Usage-Monitoring-Information AVP in a CCR-Update message indicates the quota amount used by a user. Its format is as follows: Usage-Monitoring-Information::= < AVP Header: 1067 > [ Monitoring-Key ]----This sub-AVP must be carried. [ Used-Service-Unit ]----Indicates the used quota amount, including the traffic volume or duration quota. [ Usage-Monitoring-Level ]----Indicates the monitoring level (session level or rule level). |
<CC-Request> ::= < Diameter Header: 272, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ CC-Request-Type } [ Note 1 ]
{ CC-Request-Number } [ Note 2 ]
[ Framed-IP-Address ] [ Note 3 ]
[ Framed-IPv6-Prefix ] [ Note 4 ]
[ Event-Trigger ] [ Note 5 ]
*[ Usage-Monitoring-Information ] [ Note 6 ]
[ Monitoring-Key ]
[ Usage-Monitoring-Level ]
[ Used-Service-Unit ]
[ CC-Time ]
[ CC-Total-Octets ]
*[ AVP ]
[ Usage-Monitoring-Report ]
[ Usage-Monitoring-Support ]
{ Termination-Cause } [ Note 7 ]
[ Usage-Monitoring-Information ]
[ Monitoring-Key ]
[ Usage-Monitoring-Level ]
[ Used-Service-Unit ]
[ CC-Time ]
[ CC-Total-Octets ]
[ Usage-Monitoring-Report ]
[ Usage-Monitoring-Support ]
Note Index |
Note Description |
|---|---|
[Note1] |
In the IP-CAN session termination authorization request message, the value of the CC-Request-Type AVP is TERMINATION_REQUEST. The PCRF usually focuses on only the Termination-Cause AVP in the IP-CAN session termination authorization request message. |
[Note2] |
The CC-Request-Number AVP is used to distinguish requests or responses in a session because a Session-Id is globally unique. The value of CC-Request-Number increases by 1 each time a session is modified. |
[Note3] |
An IP-CAN session authorization request message must include the Framed-IP-Address AVP or Framed-IPv6-Prefix AVP (specifically, it must contain a user address). Otherwise, the message is considered invalid. If a request message carries both of the preceding AVPs, the PCRF uses an IPv4 address as the user address. |
[Note4] |
Either an IPv6 address or the Frame-IP-Address AVP must exist. |
[Note5] |
The Event-Trigger AVP is set to USAGE-REPORT, indicating that usage is monitored and reported. |
[Note6] |
The Usage-Monitoring-Information AVP carries the accumulated usage (quota fragment) of a user. Its format is as follows: Usage-Monitoring-Information::= < AVP Header: 1067 > [ Monitoring-Key ]----If this AVP is not carried, the monitoring is at session level. [ Used-Service-Unit ]----Indicates the used quota amount, including the traffic volume or duration quota. [ Usage-Monitoring-Level ]----Indicates the monitoring level (session level or rule level). |
[Note7] |
The Termination-Cause AVP indicates the cause of the user's logout. When a user logs out normally, this AVP is set to DIAMETER_LOGOUT 1. Other values indicate that a user logs out abnormally. For details, see related AVP description. |
33GPP TS 29.212 V9.7.0 clause 5.6.2