Overview
3GPP2 Standard Pre-paid Billing Overview
Custom Pre-paid Billing Overview
License Requirements
Configuring Standard 3GPP2 Pre-paid Billing
IMPORTANT:
configure
context <context_name>
subscriber default
prepaid
3gpp2 accounting
end
configure
context <context_name>
subscriber
name <alias_def_sub>
prepaid
3gpp2 accounting
end
Configuring Pre-paid Billing With Custom Behavior
IMPORTANT:
IMPORTANT:
IMPORTANT:
configure
context <context_name>
subscriber default
prepaid custom
end
configure
context <context_name>
subscriber
name <alias_def_sub>
prepaid custom
end
3GPP2 Pre-paid Attributes
Attribute | Sub-attribute | Description |
---|---|---|
3GPP2-Pre-Paid-Acct-Capability
|
This attribute is
for setting the prepaid accounting capability.
|
|
Available-In-Client
|
The optional Available-In-Client
Sub-Type, generated by the PrePaid client, indicates the PrePaid
Accounting capabilities of the client in the PDSN or HA and shall
be bitmap encoded.
|
|
Selected-For-Session
|
The optional Selected-For-Session
Sub-Type, generated by the PrePaid server, indicates the PrePaid
Accounting capability to be used for a given session.
|
|
3GPP2-Pre-Paid-Accounting-Quota
|
This attribute specifies
the characteristics for PrePaid accounting of the volume and/or
duration of a packet data session. It shall be present in all on-line
RADIUS Access-Request and on-line RADIUS Access-Accept messages
and may be included in other RADIUS Access-Accept messages. Non-used
Sub-Types by the PPC and PPS shall be omitted.
|
|
Quota-Identifier
|
The Quota-Identifier
Sub-Type is generated by the PrePaid server at allocation of a Volume and/or
Duration Quota. The on-line quota update RADIUS Access-Request message
sent from the PPC to the PPS shall include a previously received Quota-Identifier.
|
|
Volume-Quota
|
The optional Volume-Quota
Sub-Type is only present if Volume Based charging is used. In RADIUS
Access-Accept message (PPS to PPC direction), it indicates the Volume
(in octets) allocated for the session by the PrePaid server. In on-line
RADIUS Access-Request message (PPC to PPS direction), it indicates
the total used volume (in octets) for both forward and reverse traffic
applicable to PrePaid accounting13. If a Tariff Switch condition
was reached during the session, this Sub-Type contains the complete (before
and after) volume used, while the Volume-Used-After-Tariff-Switch
attribute contains the volume used after the tariff switch condition.
|
|
Volume-Quota-Overflow
|
The optional Volume-Quota-Overflow
Sub-Type is used to indicate how many times the Volume-Quota counter
has wrapped around 2^32 over the course of the service
being provided.
|
|
Volume-Threshold
|
The Volume-Threshold
Sub-Type shall always be present if Volume-Quota is present in a RADIUS
Access-Accept message (PPS to PPC direction). It is generated by
the PrePaid server and indicates the volume (in octets) that shall
be used before requesting quota update. This threshold should not
be larger than the Volume-Quota.
|
|
Volume-Threshold-Overflow
|
The optional Volume-Threshold-Overflow Sub-Type
is used to indicate how many times the Volume-Threshold counter
has wrapped around 2^32 over the course of the service
being provided.
|
|
Duration-Quota
|
The optional Duration-Quota
Sub-Type is only present if Duration Based charging is used. In RADIUS
Access-Accept message (PPS to PPC direction), it indicates the Duration
(in seconds) allocated for the session by the PrePaid server. In on-line
RADIUS Access-Accept message (PPC to PPS direction), it indicates
the total Duration (in seconds) since the start of the accounting
session related to the Quota-ID.
|
|
Duration-Threshold
|
The Duration-Threshold
Sub-Type shall always be present if Duration-Quota is present in
a RADIUS Access-Accept message (PPS to PPC direction). It represents
the duration (in seconds) that shall be used by the session before
requesting quota update. This threshold should not be larger than
the Duration-Quota and shall always be sent with the Duration-Quota.
|
|
Update-Reason
|
The Update-Reason
Sub-Type shall be present in the on-line RADIUS Access-Request message
(PPC to PPS direction). It indicates the reason for initiating the
on-line quota update operation. Update reasons 4, 5, 6, 7 and 8
indicate that the associated resources are released at the client
side, and therefore the PPS shall not allocate a new quota in the
RADIUS Access-Accept message.
|
|
Pre-Paid-Server
|
The optional, multi-value
PrePaid-Server indicates the address of the serving PrePaid System.
If present, the Home RADIUS server uses this address to route the
message to the serving PrePaid Server. The attribute may be sent
by the Home RADIUS server. If present in the incoming RADIUS Access-Accept
message, the PDSN shall send this attribute back without modifying
it in the subsequent RADIUS Access-Request message, except for the
first one. If multiple values are present, the PDSN shall not change
the order of the attributes.
|
Pre-paid Attributes
Attribute | Description |
---|---|
SN-Prepaid-Inbound-Octets
|
If only SN-Prepaid-Inbound-Octets
is in the Access-Accept, and the others are not, then the number
of outbound credits is infinite.
|
SN-Prepaid-Outbound-Octets
|
If only SN-Prepaid-Outbound-Octets
is in the Access-Accept, and the others are not, then the number
of inbound credits is infinite.
|
SN-Prepaid-Total-Octets
|
If only SN-Prepaid-Total-Octets
is in the Access-Accept, and the others are not, then pre-paid credits
is only enforced on the total byte throughput.
|
SN-Prepaid-Timeout
|
SN-Prepaid-Timeout
can be used alone or in combination with the other attributes. This
integer RADIUS attribute includes a time limit in seconds. Regardless
of the values of the Octet counters, the session should send a new
authorization request upon timer expiration.
|
SN-Prepaid-Watermark
|
SN-Prepaid-Watermark
is optional with any of the attributes. If it is not included it
defaults to the CLI default subscriber configuration, which defaults
to a value of 10%. This watermark applies to any of the
pre-paid attributes being enforced.
|