Nokia 7750 - 2.2.5 Accounting On-Line Charging

RADIUS ATTRIBUTES REFERENCE GUIDE
RELEASE 14.0.R4
RADIUS Attributes Reference
Issue: 01 3HE 10793 AAAB TQZZA 01 85
2.2.5 Accounting On-Line Charging
26-6527-212 Alc-BGP-IPv6-Import-Policy 0 0-1 0
26-6527-213 Alc-BGP-IPv6-PeerAS 0 0-1 0
Table 13 Business Access (Applicability) (Continued)
Attribute ID Attribute Name Access
Request
Access Accept CoA Request
Table 14 Accounting: On-Line Charging (Description)
Attribute ID Attribute Name Description
26-6527-95 Alc-Credit-Control-
CategoryMap
Refers to a preconfigured category-map (configure subscriber-mgmt
category-map category-map-name) that contains credit control
information for up to sixteen (16) predefined categories The category-
map-name can also be assigned via the ludb, or credit-control-policy if
the attribute is omitted. This attribute is ignored if the host has no credit-
control-policy defined in its sla-profile instance. Strings with length
above the Limits are treated as a setup failure.
26-6527-96 Alc-Credit-Control-
Quota
Defines a volume and time quota per category. Either volume or time
monitoring is supported and the operational credit-type (volume or time)
is taken from the category map if both volume and time-quota in this
attribute are non-zero. The operational credit-type becomes time if the
volume-quota is zero and volume if the time-quota is zero. The Credit
Expired becomes true and the corresponding Out Of Credit Action is
triggered if both time and volume-quota are zero in the initial
Authentication-Accept or CoA. Value zero for both time and volume-
quota in additional Authentication Accepts (triggered by credit refresh or
re-authentication) are interpreted as no extra credit granted and does
not influence the current available credit, were non-zero values reset
the current available credit. For CoA requests both Alc-Credit-Control-
CategoryMap and Alc-Credit-Control-Quota attributes needs to be
included. For RADIUS-Access Accepts this is not mandatory and either
both or one of the two attributes can come from pre-defined values from
the node. Volume quota values outside the defined limits are treated as
an error condition. Time quota values above the defined limits are
accepted and capped at maximum value. If more attributes are present
than allowed by the limits, it is treated as a setup failure.