Datasheet

© 2006 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com.
Page 4 of 11
Ease of User-Profile Configuration
The destinations for which the Cisco CSG will generate billing records on a per-user basis can be specified with command-line interface (CLI)
commands. Destinations are specified by domains, ports, and protocols, and can also be specified using wildcards. Policies can be used to apply
URL and header maps. For prepaid or managed subscribers, these content rules can be grouped logically into services that can be included or
excluded from user billing plans.
Open Interface with Multiple Billing Agents
The Cisco CSG collects content information and feeds it to a billing agent. The billing agent aggregates all of the information about a data session
and formats it to be used by the rating and billing engines. The base protocols used to communicate with the billing mediation or billing devices
are standard and open, and provide facilities for reliable transmission and failover in the event that one of the billing systems becomes unavailable.
This enables the Cisco CSG to interface with whatever billing agent the customer chooses and to provide robust reporting, after this protocol is
implemented.
Use of Content for Data Mining
Cisco CSG capabilities are not restricted to billing applications. Service providers can now gather subscriber network, service, and content usage
data across their networks. An operator can apply business intelligence to the collected information to better understand user transaction behaviors
and apply that knowledge to marketing and partnership strategies. Traffic patterns can also be analyzed for use in quality-of-service (QoS) plans.
Popular sites can be identified and approached with real data to justify opportunities for content-delivery hosting.
Content Filtering
In conjunction with Cisco partners, the Cisco CSG provide support for dynamic content filtering. Service providers can provide personal filtering
based upon blacklists and whitelists, allowing access to content deemed appropriate or on a paid-for basis.
NEW FEATURES IN CISCO CSG RELEASE 7
HTTP IP Byte Count Reporting
The Cisco CSG will report the total number of IP bytes of each HTTP transaction transferred between a client and a server. Bytes that can be
associated with a particular transaction will be charged to the matching service (content or policy). For the remaining subset that could not be
associated with any particular transaction, the intention is to allow the billing system to tally the unassociated byte volumes provided by the CSG
and charge that to “network overhead” if the customer chooses to do so. The Cisco CSG does not itself implement a network overhead service.
Known User Table Entry Timeout
In order to ensure subscriber entries are removed from the known user table (KUT), the Cisco CSG now allows the idle timer for a user entry to
start when all the user’s sessions have terminated. When the idle timer expires, a Packet of Disconnect (PoD) message will be sent if it is specified
and configured. If a PoD is not sent, the KUT entry is deleted. If a PoD is sent, the KUT entry is deleted when the PoD message is ACKed (message
type 41), NAKed (message type 42), or when all retries have been sent; the RADIUS Stop message does not have to be received by the Cisco CSG.
RTSP Pause Support
The Cisco CSG allows for the monitoring of the RTSP control session between the RTSP client and server, and scans for PAUSE and PLAY
methods. When a PAUSE method is detected, it initiates an event to inform the prepaid service to stop charging for duration billing. Subsequently,
when a PLAY method is detected, it initiates an event to inform the prepaid service to resume the charging for duration billing.