Modes of Operation
The Usage-based Billing feature can operate in three modes:
•
File Mode
—
In file mode, the CMTS collects the billing record information and writes the billing records
to a file on a local file system, using a file name that consists of the router
’
s hostname followed by a
timestamp of when the file was written. A remote application can then log into the CMTS and transfer
the billing record file to an external server where the billing application can access it.
The remote application can use the Secure Copy Protocol (SCP) or the Trivial File Transfer Protocol (TFTP)
to transfer the file. After a successful transfer, the remote application then deletes the billing record file, which
signals the CMTS that it can create a new file. The remote application can either periodically log into the
CMTS to transfer the billing record file, or it can wait until the CMTS sends an SNMPv2 trap to notify the
application that a billing record file is available.
•
Streaming Mode
—
In streaming mode, the CMTS collects the billing record information and then
regularly transmits the billing record file to an application on an external server, using either a non-secure
TCP connection or a secure sockets layer (SSL) connection. The billing record data collected is streamed
in real time; and if streaming is unsuccessful, then the SAMIS data is sent only at the next interval.
If the CMTS fails to establish a successful connection with the external server, it retries the connection between
one to three times, depending on the configuration. If the CMTS continues to fail to connect with the external
server, the Cisco CMTS sends an SNMPv2 trap to notify the SNMP manager that this failure occurred.
In streaming mode, you can configure the CMTS to transmit the billing record file at regular intervals. Typically,
the interval chosen would depend on the number of cable modems and the size of the billing record files that
the CMTS produces.
•
IPDR Mode
—
In the IPDR mode, the IPDR export process communicates with IPDR Collectors. The
architecture supports multiple Collectors distinguished by priority value for failover purposes. The
smaller the number of Collectors, the higher is the priority value. Associating one session to two or more
Collectors with the same priority value is regarded as random priority. At any given time, data is sent
to only the available highest priority Collector. If the highest priority Collector connection fails due to
any reason, the data is sent to the next available highest priority Collector. After a higher priority Collector
comes back online, it will fail over again. Depending on the network configuration, you can have different
primary Collectors for different IPDR sessions. For example, there may be a billing Collector or a
diagnostic Collector.
Billing Record Format
Each billing record is an ASCII text file using XML formatting to encode the billing record objects that are
required by the DOCSIS specifications. This file can be read by any billing application that can be configured
to parse XML data files.
The table lists the objects that are contained in each billing record that the CMTS generates. This table shows
the object
’
s name, as it appears in the billing record, and a description of that object.
Cisco cBR Series Converged Broadband Routers Troubleshooting and Network Management Configuration
Guide for Cisco IOS XE Fuji 16.8.x
130
Usage-Based Billing (SAMIS)
Modes of Operation