2 System Overview Introduction

2 System Overview Introduction
CH A P T E R
2
System Overview
Published: December 23, 2013, OL-30611-01
Introduction
The Cisco Service Control Application for Broadband (Cisco SCA BB) is the Cisco Service Control
solution that allows broadband service providers to gain network-traffic visibility, to control the
distribution of network resources, and to optimize traffic in accordance with their business strategies. It
enables service providers to reduce network costs, improve network performance and customer
experience, and create new service offerings and packages. This chapter contains the following sections:
•
System Components, page 2-1
•
Subscribers and Subscriber Modes, page 2-3
•
Service Configuration, page 2-6
System Components
The Cisco Service Control solution consists of four main components:
•
The Cisco Service Control Engine (Cisco SCE) platform—A flexible and powerful dedicated
network-usage monitor that is purpose-built to analyze and report on network transactions at the
application level.
For more information about the installation and operation of the Cisco SCE platform, see the Cisco
SCE Platform Installation and Configuration Guides.
•
The Cisco Service Control Subscriber Manager—A middleware software component that is used
where dynamic binding of subscriber information and policies are required. The Subscriber
Manager manages subscriber information and provisions it in real time to multiple Cisco SCE
platforms. The Subscriber Manager can store subscriber policy information internally, and act as a
stateful bridge between the AAA system (such as RADIUS and DHCP) and the Cisco SCE
platforms.
For more information about the installation and operation of the Subscriber Manager, see the Cisco
Service Control Management Suite Subscriber Manager User Guide.
The Quota Manager (QM) is an optional component of the Subscriber Manager. It enables Service
Control solution providers to manage subscriber quota across subscriber sessions with a high degree
of flexibility.
Cisco Service Control Application for Broadband User Guide
OL-30611-01
2-1
Chapter 2 System Overview
System Components
For more information about the installation and operation of the QM, see the Cisco Service Control
Management Suite Quota Manager User Guide.
•
The Cisco Service Control Collection Manager (CM)—An implementation of a collection system
that receives Raw Data Records (RDRs) from one or more Cisco SCE platforms. It collects usage
information and statistics, and stores them in a database. The CM also converts subscriber usage
information and statistics into simple text-based files for further processing and collection by
external systems.
For more information about the installation and operation of the CM, see the Cisco Service Control
Management Suite Collection Manager User Guide.
Together, the Cisco SCE platform, the Cisco Service Control Collection Manager, and the Cisco Service
Control Subscriber Manager are designed to support detailed classification, analysis, reporting, and
control of IP network traffic. The Cisco Service Control Collection Manager and the Cisco Service
Control Subscriber Manager are optional components; not all deployments of the Cisco Service Control
solution require them. Sites that employ third-party collection and reporting applications, those that do
not require dynamic subscriber-aware processing, and those that use a RADIUS or DHCP sniffing option
may not require all of these components.
Figure 2-1 illustrates the flow of information in the Cisco Service Control solution.
•
Horizontal flow—Represents traffic between subscribers and an IP network.
The Cisco SCE platform monitors traffic flow.
•
Vertical flow—Represents transmission of the Raw Data Records (RDRs) from the Cisco SCE
platform to the CM.
The Subscriber Manager may be added to the control flow to provide subscriber data. This allows
Cisco SCA BB to conduct subscriber-level analysis and control.
Figure 2-1
Flow of Information in Cisco SCA BB
RADIUS/DHCP
Login/Logout
Service Control
Subscriber Manager
Subscriber
provisioning
Router/
Switch
Broadband
subscribers
Router/
Switch
PWR A
MNG 1
LINK/
ACTIVE 10/100/
1000
MNG 2
CONSOLE
AUX
LINK/
ACTIVE 10/100/
1000
PWR B
STATUS
BYPASS
Internet
Cisco SCE
2000
4xGBE Series
LINK RX
TX
LINK RX
TX
LINK RX
TX
RX
MM
LINK RX
TX
TX
RX
MM
TX
RX
MM
TX
GBE-1
SUB
LINE
NET
RX
MM
TX
GBE-2
SUB LINE/CASCADE
Aggregation
device
(CMTS,BRAS,
switch, etc.)
92818
NET
Usage information
and statistics
Service Control
Collection Manager
Cisco Service Control Application for Broadband User Guide
2-2
OL-30611-01
Chapter 2 System Overview
Subscribers and Subscriber Modes
Subscribers and Subscriber Modes
One of the fundamental entities in the Cisco Service Control solution is a subscriber. A subscriber is the
most granular entity on which Cisco SCA BB can individually monitor, account, and enforce a policy.
In the most granular instance of the Cisco SCA BB system a subscriber is an actual customer of the
service provider on whom an individual policy is implemented. However, you may also configure Cisco
SCA BB to monitor and control traffic at a higher granularity, such as when monitoring or controlling
traffic by subnets or aggregation devices.
One of the most important decisions you must take when designing a service control solution is what
subscribers in the system represent. This decision determines which subscriber mode is used, which in
turn determines what (if any) integrations are required and what policies to define. The following
sections describe the different subscriber modes supported and, for each mode, the functions supported,
any prerequisites, and the components needed.
Cisco SCA BB supports the following four subscriber modes:
•
Subscriberless mode—No subscribers are defined. Control and link-level analysis functions are
provided at a global platform resolution.
•
Anonymous subscriber mode—IP addresses are controlled and monitored individually. The Cisco
SCE platform automatically identifies IP addresses as they are used and assigns them to a package.
•
Static subscriber mode—Incoming IP addresses are bound and grouped statically into “subscribers”
as configured by the system operator.
•
Subscriber-aware mode—Subscriber information is dynamically bound to the IP address currently
in use by the subscriber. Subscriber-aware mode can be achieved by integrating Cisco SCA BB with
the system (RADIUS, DHCP) that assigns IP addresses to subscribers, or by sniffing this
information. Policy information is either administered to Cisco SCA BB directly or provisioned
dynamically via an integration.
Subscriberless Mode
Subscriberless mode is the choice for sites where control and analysis functions are required only at a
global platform resolution. It can be used, for example, to monitor and control the total P2P traffic over
the link.
Subscriberless mode requires no integration; hence, the Cisco Service Control Subscriber Manager is
not required.
Note
The number of subscribers or inbound IP addresses does not influence the Subscriberless mode. Hence,
the total number of subscribers using the monitored link is unlimited from the point of view of the Cisco
SCE platform.
Anonymous Subscriber Mode
Anonymous subscriber mode provides the means to analyze and control network traffic at
subscriber-inbound IP address granularity.
Use this mode when:
•
You do not require subscriber-differentiated control or subscriber-level quota tracking
Cisco Service Control Application for Broadband User Guide
OL-30611-01
2-3
Chapter 2 System Overview
Static Subscriber Mode
•
Analysis on an IP level is sufficient
•
When offline IP-address/subscriber binding can be performed
For example, you can identify which subscribers generate the most P2P traffic by identifying the top IP
addresses and correlating them to individual subscribers using RADIUS or DHCP logs. The total
bandwidth of P2P traffic allowed for each subscriber can also be limited.
Anonymous subscriber mode requires no integration or static configuration of the IP addresses used, so
the Cisco Service Control Subscriber Manager is not required.
In this mode, ranges of IP addresses are configured directly on the Cisco SCE platform. Cisco SCE
Platform dynamically creates “anonymous” subscribers for these IP addresses, using the IP address as
the subscriber name.
Note
The total number of concurrently active anonymous subscribers supported by the Cisco SCE platform is
the same as the total number of concurrently active subscribers.
Static Subscriber Mode
Static subscriber mode binds incoming IP addresses together into groups, so that traffic from and to
defined subscribers can be controlled as a group. For example, you can define all traffic from and to a
particular network subnet (used by multiple subscribers concurrently) as a (virtual) “subscriber” and
controlled or viewed as a group.
Static subscriber mode supports cases in which the entity controlled by the Cisco Service Control
solution uses a constant IP address or address range that does not change dynamically, such as:
•
Environments where the subscriber IP addresses do not change dynamically via, for example, DHCP
or RADIUS
•
Deployments in which a group of subscribers using a common pool of IP addresses (such as all those
served by a particular aggregation device) are managed together to provide a shared bandwidth to
the entire group
The system supports the definition of static subscribers directly on a Cisco SCE platform; it does not
require external management software (such as the Cisco Service Control Subscriber Manager). Use the
Cisco SCE platform CLI to define the list of subscribers, their IP addresses, and the associated package.
Subscriber-Aware Mode
In subscriber-aware mode, the subscriber information (OSS ID and policy) that is dynamically bound to
the (IP) address currently in use by the subscribers are populated on the Cisco SCE.
The subscriber information is populated regardless of the IP address in use and provides differentiated
and dynamic control per subscriber and subscriber-level analysis. Use this mode to control and analyze
traffic on a subscriber level, to monitor subscriber usage, and to assign and enforce different control
policies (packages) for different subscribers.
In this mode, the Cisco Service Control Subscriber Manager may provision the Cisco SCE platform with
subscriber information.
Cisco Service Control Application for Broadband User Guide
2-4
OL-30611-01
Chapter 2 System Overview
Subscriber Modes: Summary
Subscriber Modes: Summary
Table 2-1 summarizes the different subscriber modes supported by the system.
Table 2-1
Summary of Subscriber Modes
Mode
Subscriberless
mode
Features Supported
•
Global (platform-level)
analysis and control
Main Advantages
•
No subscriber configuration
required.
Use for...
Global control solution or
subscriber-level analysis.
Examples:
Anonymous
subscriber mode
Static subscriber
mode
Subscriber-aware
mode
•
Global analysis and control
•
Individual IP address-level
analysis and control
•
Global analysis and control
•
Control based on individual
or group IP addresses as
configured statically to the
Cisco SCE platform
•
Full system functionality
•
No subscriber configuration
required; only define
subscriber IP address ranges
used.
•
Provide subscriber-level
control without integration.
•
Control P2P uploads at
peering points.
•
Limit total bandwidth of P2P
to a specified percentage.
IP-level analysis or control that is
not differentiated per subscriber,
and where offline
IP-address/subscriber binding is
sufficient.
Examples:
•
Limit P2P bandwidth per
subscriber.
•
Identify top subscribers by
identifying top IP addresses
and correlating them with
RADIUS or DHCP logs.
Control of traffic of groups of
subscribers.
•
One-time static subscriber
configuration, with no
integration requirements.
•
Manage subscriber traffic in
logical groups.
•
Differentiated and dynamic
control per subscriber.
Control and analysis of traffic on
a subscriber level.
•
Subscriber-level analysis,
regardless of IP address in
use.
Examples:
Example:
•
Assign a bandwidth limit for
P2P traffic for each group of
subscribers using a single
CMTS device.
•
Monitor subscriber-usage,
regardless of IP addresses.
•
Assign different control
policies (packages) to
different subscribers, and
change packages
dynamically.
Cisco Service Control Application for Broadband User Guide
OL-30611-01
2-5
Chapter 2 System Overview
Service Configuration
Service Configuration
Service configuration defines the way the Cisco SCE platform analyses and controls traffic. In general
terms, as illustrated in Figure 2-2, service configuration defines the following:
•
Protocol and service classification
•
Packages and policies
•
Bandwidth controllers
•
Global controllers
Figure 2-2
Service Configuration
Services
SCAS BB Console
and utilities
Packages
Protocols
Bandwidth controllers
Service
configuration
(PQB file)
Global controllers
PWR A
MNG 1
LINK/
ACTIVE 10/100/
1000
MNG 2
PWR B
STATUS
CONSOLE
AUX
LINK/
ACTIVE 10/100/
1000
BYPASS
Cisco SCE
2000
4xGBE Series
LINK RX
TX
LINK RX
TX
LINK RX
TX
RX
MM
LINK RX
TX
TX
RX
MM
TX
RX
MM
TX
GBE-1
SUB
LINE
NET
RX
MM
92822
Time frames
TX
GBE-2
SUB LINE/CASCADE
NET
Apply/retrieve service
configuration definition
Service configuration is accomplished using one of the following:
•
The Console
•
The Cisco SCA BB Service Configuration Utility
•
The Service Configuration API
The Cisco SCA BB Console
The Cisco SCA BB Console is a set of GUI tools that are used to manage, configure, and monitor the
solution components.
The Console is fully documented in the remainder of this guide.
The Service Configuration Utility
The Cisco SCA BB Service Configuration Utility (servconf) is a simple command-line utility that you
can use to apply PQB configuration files onto Cisco SCE platforms or to retrieve the current
configuration from a Cisco SCE platform and save it as a PQB file. The utility configures Cisco SCE
platforms with the service configuration defined in a PQB file. You can install and execute it in a
Windows or Solaris environment.
Cisco Service Control Application for Broadband User Guide
2-6
OL-30611-01
Chapter 2 System Overview
The Service Configuration API
For full documentation of servconf, see “The Cisco SCA BB Service Configuration Utility” section on
page 14-2.
The Service Configuration API
The Service Configuration API is a set of Java classes used to:
•
Program and manage service configurations
•
Apply service configurations to the Cisco SCE platforms
•
Integrated applications with third-party systems
The service configuration API allows service providers to automate and simplify management and
operational tasks.
The Service Configuration API is documented in Cisco Service Control Application for Broadband
Service Configuration API Programmer Guide.
Cisco Service Control Application for Broadband User Guide
OL-30611-01
2-7
Chapter 2 System Overview
The Service Configuration API
Cisco Service Control Application for Broadband User Guide
2-8
OL-30611-01
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising