IPDR is the data
generated or collected for various performance related metrics such as billing
information, diagnostics, network topology, signal quality monitoring, and
other management data. These data are based on the FCAPS model (Fault,
Configuration, Accounting, Performance and Security.)
The IPDR client
application communicates with the IPDR exporter using the IPDR_GET_SESSIONS
message to identify the streams provided by the exporter, and the exporter
sends responses to the client using the IPDR_GET_SESSIONS_RESPONSE message.
This data collection method is based on the
System Interface Specification (CM-SP-OSSIv3.0-I13-101008).
Beginning with Cisco IOS Release 12.2(33)SCE, the
IPDR_GET_SESSIONS_RESPONSE message includes the SessionBlock.reserved attribute
to identify the IPDR session ID. This attribute helps the Cisco CMTS router
define an IPDR session ID for each data collection mechanism supported for each
IPDR service definition. This attribute was not used in Cisco IOS Releases
earlier to Cisco IOS Release 12.2(33)SCE.
You must use a Cisco CMTS router running Cisco IOS
Release 12.2(33)SCE or later, if your IPDR client application looks for the
SessionBlock.reserved attribute in the IPDR_GET_SESSIONS_RESPONSE message.
The IPDR feature
defines methods for the collectors or network elements to collect data from the
CMTS. Below is the list of collection methodologies:
Session: In this method, the CMTS follows a schedule-based session to stream
data at a periodic time interval. A time interval is the time gap between two
adjacent sessions’ start messages. This method is managed by the CMTS in
controlling the start and stop operation of a session. The time interval
session terminates after the CMTS exports the records.
course of a one-time interval when the CMTS is streaming records, if another
time interval is expected, the CMTS will ignore the new time interval and
continue exporting the data until the previous time interval ends.
Session: In this method, the CMTS can export records at any time, when the
session is open. In other words, this method works on an open-ended session.
Ad-hoc Session: In
this method, the CMTS creates a session, allows data streaming, and closes the
session when the data export is complete or when a closing command is
A new session is
created by issuing the
session command. After, the CMTS receives the
FLOW_START message from the collector, the CMTS exporter sends a SESSION_START
message to start exporting the IPDR data from the collector. After all data is
transported, the exporter receives a ACK message from the collector, and then
sends a SESSION_STOP message to the collector. This method is known as the