A
- access lines 1
- accesses
- configuring subscriptions
- accounting
- anonymous subscriber
- attributes
- authenticated subscriber
- authentication plug-ins
- authorization plug-ins
B
C
- captive portal
- classification scripts
- conditions 1
- configuring
- descriptions
- DHCP classification, C Series Controller
- interface classification, C Series Controller
- structure
- subscriber classification, C Series Controller
- target, C Series Controller
- component interactions
- conventions
- COPS (Common Open Policy Service)
- custom RADIUS accounting plug-ins 1
- configuring
- custom RADIUS authentication plug-ins 1
- configuring
- customer support 1
D
- default retailer authentication plug-ins
- configuring
- default retailer DHCP authentication plug-ins
- configuring
- denial-of-service attacks
- DHCP (Dynamic Host Configuration Protocol)
- address assignment
- classification scripts. See classification scripts
- options
- profiles
- subscribers
- documentation
E
- enterprise
- enterprise subscribers 1
- adding
- enterprise subscribers, login process
- event publishers
- configuring
- default retailer authentication, configuring
- default retailer DHCP authentication, configuring
- description
- retailer-specific
- service-specific
- virtual router-specific
- external plug-ins
- configuring
F
- file upload settings for log rotation
- configuring
- flat file accounting plug-ins 1
- flexible RADIUS accounting plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- flexible RADIUS authentication plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- setting responses
- FTP server for log rotation
G
- general properties
- configuring
H
- HTTP proxy 1, 2
- HTTPS traffic
I
- interface classification scripts. See classification scripts
- interim accounting, configuring on SAE
- internal plug-ins
- configuring
L
- LDAP authentication plug-in 1
- configuring
- limiting subscribers plug-in 1
- configuring
- log rotation
- overview
- logging
- login events, description
- login process
- login registration
- configuring
- logout process, residential
M
- managers
- manuals
N
- NAT (Network Address Translation)
- notice icons
P
- plug-ins
- activating service sessions
- authentication
- authorization
- basic RADIUS accounting 1
- basic RADIUS authentication 1
- creating subscriber sessions
- custom RADIUS accounting 1
- custom RADIUS authentication 1
- defining RADIUS packets
- DHCP address assignment
- event publishers. See event publishers
- external
- flat file accounting 1
- flexible RADIUS accounting 1
- flexible RADIUS authentication 1
- internal 1
- LDAP authentication 1
- limiting subscribers 1
- state synchronization
- tracking
- policy groups
- policy management
- PPP subscribers
- prevention, use of unauthorized resources
- protocols
- proxy HTTP 1, 2
- proxy request management
- public addresses, VPNs
Q
R
- RADIUS accounting
- RADIUS attributes
- defining in RADIUS plug-ins
- examples, defining in RADIUS plug-ins
- RADIUS client library, custom RADIUS plug-ins
- RADIUS packets, customizing in plug-ins
- RADIUS peers
- configuring in plug-ins
- RADIUS plug-ins 1, See also plug-ins
- redirect server
- assessing load
- configuration statements
- configuring
- configuring DNS server for
- configuring HTTP proxy support
- configuring redundant
- directory connection
- failover
- file extensions
- logging
- number of requests
- protection against denial-of-service attacks
- redundancy 1, 2, 3
- static route to router
- traffic definition
- verifying
- redundancy
- residential subscribers 1
- adding
- login process. See login process
- retailers
- subscribers 1
- router subscribers 1
- adding
- routing instances
- routing scheme
S
- SAE (service activation engine)
- classification scripts. See classification scripts
- login events
- login process. See login process
- SAE (service activation engine), configuring
- service activation engine. See SAE
- service sessions
- sites 1, 2, 3
- subscriber 1
- state synchronization plug-in interface
- configuring
- static IP subscribers, login process
- static routing
- subscriber classification scripts. See classification scripts
- subscriber folders 1
- adding
- subscriber sessions
- subscribers
- 3gpp attributes (Gx router driver)
- adding
- enterprise 1
- inheriting properties
- inheriting subscriptions
- residential 1
- retailer 1
- router 1
- sessions
- sites 1
- types
- subscriptions 1
- access, configuring
- an orderly deactivation, activation order, specifying
- configuring
- multiple per subscriber
- support, technical See technical support
T
- targets. See classification scripts
- technical support
- text conventions defined
- tracking plug-ins 1
- configuring
U
- UDP ports
- User Datagram Protocol. See UDP
V
- validating
- virtual private networks. See VPNs
- VPNs (virtual private networks)
- adding
- configuration requirements
- configuration statements
- extranet clients, modifying
- invalid subscriptions
- modifying
- routing schemes
- using NAT
- validating
Download This Guide
Subscriptions and Activations
Each subscriber purchases a set of services; this purchase is known as a subscription. Information about the subscriptions is stored in the directory and is used by a residential service selection portal application to generate controls that enable the subscriber to:
- Activate and deactivate subscriptions.
- Subscribe to services.
- Configure subscriptions to be automatically activated.
The service selection application can be either a Web application or an API. When the service selection application is a Web application, the controls are webpages with buttons and links to click on (see Figure 13 and Figure 14). However, the service selection application provides an open API that makes it possible to build applications that are controlled by mechanisms other than webpages. For instance, customers can build service selection applications that are controlled by applications running in the system tray area of the Windows task bar. This deployment consolidates the control of subscribers’ active network services and the speed of their Internet connection, along with their control of other aspects of their PC, such as the clock settings and audio volumes.
Figure 13: Service Activation Page
Figure 14: Subscription Activation Page
Many of the activation and deactivation interactions work in the same way, whether the subscriber is a residential subscriber or an enterprise subscriber. However, some interactions apply only to enterprise subscribers.
Subscription Activation Interactions
Clicking a button on the webpage to activate a service session causes the SAE to download the policies associated with the service to the subscriber’s IP interface on the router. Figure 15 shows the interactions among the components shown in Residential Subscriber Login and Processes during the activation process. This scenario assumes that the subscriber has already logged in.
Figure 15: Subscription Activation
The activation sequence is as follows:
- Before the subscription is activated, the subscriber makes a request to the corresponding subscription resource in the service-controlled area.
- A default policy that matches the request on the router causes the router to redirect the request to the SAE.
- The SAE responds to the request with a help desk webpage, requesting that the subscriber activate the subscription before trying to access the resource.
- The subscriber clicks a button on the service selection portal webpage, requesting the activation of the subscription.
- The SAE sends a COPS or BEEP decision (DEC) message to
the router, requesting the installation of policies for the subscription
on the subscriber’s IP interface on the router, as well as service
session information.
At start time, the SAE loads all services and policy templates from the directory. At activation time, the policy templates for the service are instantiated with values that are determined at activation, such as the subscriber’s IP address. The router stores session information so that if the SAE fails, the subscribers can continue using their active subscriptions. If the SAE fails, the router connects to a backup SAE. The backup SAE synchronizes all session information and then takes over management of all active subscribers on the router.
- The router responds with a report (RPT) message acknowledging the decision message.
- The SAE sends an accounting start message to the RADIUS server.
- The RADIUS server acknowledges the accounting start message.
- The SAE responds to the subscriber’s activation request, indicating that the subscription is active.
- The subscriber may now retry the request for access to the controlled resource.
- This time, the request to the controlled resource matches the policy from the newly activated subscription, so the router allows the request to be routed normally. Depending on the policy, the router may also apply QoS processing.
- If interim accounting is enabled, the SAE periodically sends a decision message requesting usage data.
- The router responds with a report message that contains usage data for the subscription. The usage data consists of the number of bytes and packets that the policies processed for the subscription.
- The SAE stores the usage data in interim accounting records in the RADIUS server.
- The RADIUS server acknowledges the interim accounting record.
Subscription Deactivation Interactions
Clicking a button on the webpage to deactivate a service causes the SAE to request that the router remove the policies for the service from the subscriber’s IP interface on the router.
Figure 16 shows the interactions among the components shown in Residential Subscriber Login and Processes during the subscription deactivation process. This scenario assumes that the subscriber has already logged in.
Figure 16: Subscription Deactivation
The deactivation sequence is as follows:
- The subscriber sends a request to deactivate a subscription to a resource in the service-controlled area.
- The request matches a policy that allows the request to be forwarded to the resource in the service-controlled area.
- The subscriber clicks on a field on a webpage to request that the SAE deactivate the subscription.
- As a result, the SAE sends a COPS or BEEP decision (DEC) message to the router to remove policies for the subscription from the subscriber interface and the service session from memory.
- The router acknowledges the decision message with a report (RPT) message that contains service usage. The usage is the number of bytes and packets that the policies processed for the subscription.
- An accounting stop record that includes the subscription usage information is written in the RADIUS server.
- The RADIUS server acknowledges the accounting message.
- The SAE sends a message to the subscriber, informing the subscriber that the subscription has been deactivated.
- Because the policy for the subscription was removed from the subscriber interface on the router, any request for access is directed to the SAE.
- The subscriber may now retry to request access to the controlled resource.
- As was the case before the subscription was activated, the SAE generates a help desk webpage response that is relayed to the subscriber.
Related Documentation
- Subscriptions Overview
- Automatic Activation at Login
- Residential Subscriber Login and Processes
- Configuring Subscriptions (SRC CLI)
- Configuring Accesses (SRC CLI)
