Cisco Cisco IOS Software Release 12.4(2)XB6
217
Cisco Packet Data Serving Node (PDSN) Release 4.1 for Cisco IOS Release 12.4(15)XR7
Cisco Packet Data Serving Node (PDSN) Release 4.1 for Cisco IOS Release 12.4(15)XR7
PDSN Accounting
The CDMA2000 packet accounting model is divided into radio specific parameters collected by the radio
network elements, and the IP network specific parameters collected by the serving PDSN. In
conformance with the packet accounting procedures specified in TIA/EIA/IS-835-D, the PDSN merges
the radio specific parameters for a given user session with the IP network specific ones to form a Usage
Data Record (UDR). After merging the parameters, the PDSN sends the UDR to the local RADIUS
server at trigger events specified. The PDSN maintains the UDR until it receives positive
acknowledgment from the RADIUS server indicating that the RADIUS server has correctly received the
UDR.
network elements, and the IP network specific parameters collected by the serving PDSN. In
conformance with the packet accounting procedures specified in TIA/EIA/IS-835-D, the PDSN merges
the radio specific parameters for a given user session with the IP network specific ones to form a Usage
Data Record (UDR). After merging the parameters, the PDSN sends the UDR to the local RADIUS
server at trigger events specified. The PDSN maintains the UDR until it receives positive
acknowledgment from the RADIUS server indicating that the RADIUS server has correctly received the
UDR.
Flow Based Accounting
The Cisco PDSN supports multiple user sessions per mobile station. Each of these user sessions is
termed a flow. For each mobile station, one Simple IP based flow and one or more Mobile IP based flows
can be supported. Each flow is identified by a unique IP address. Accounting procedures for generating
a separate UDR for each flow is called flow based accounting.
termed a flow. For each mobile station, one Simple IP based flow and one or more Mobile IP based flows
can be supported. Each flow is identified by a unique IP address. Accounting procedures for generating
a separate UDR for each flow is called flow based accounting.
The Cisco PDSN supports flow based accounting. As per TIA/EIA/IS-835-D specifications, each flow
is identified by a unique Correlation-ID. Accounting start/stop message pair for each flow is correlated
by unique Accounting-Session-ID.
is identified by a unique Correlation-ID. Accounting start/stop message pair for each flow is correlated
by unique Accounting-Session-ID.
While creating UDRs for flow based accounting, radio specific accounting parameters are common to
all flows. IP network specific parameters, such as uplink and downlink octet counts are specific to each
flow and are identified by the unique IP address assigned to that flow. The PDSN creates UDR for each
flow by merging the radio specific parameters and the IP network specific parameters. These UDRs are
forwarded to the RADIUS server via accounting-request (start, stop, interim) messages.
all flows. IP network specific parameters, such as uplink and downlink octet counts are specific to each
flow and are identified by the unique IP address assigned to that flow. The PDSN creates UDR for each
flow by merging the radio specific parameters and the IP network specific parameters. These UDRs are
forwarded to the RADIUS server via accounting-request (start, stop, interim) messages.
The following RADIUS attributes are contained in the UDR sent by the PDSN.
Table 13
In Accounting Start Record
Attribute Name
TIA/EIA/IS-835-B
Type/Subtype
NAS-IP-Address
D2
4
NAS-Port
5
NAS-Port-Type
61
User-Name
B2
1
Calling-Station-Id
A1
31
Acct-Status-Type
40
Acct-Delay-Time
41
Acct-Authentic
45
Service-Type
6
Acct-Session-Id
C1
44
Framed-Protocol
7
Framed-IP-Address
B1
8
Event-Timestamp
G4
55
CDMA-Correlation-ID
C2
26/44