A
- access DNs
- accounting
- ACP (Admission Control Plug-In)
- redundancy
- ACP congestion point usage trap
- ACP. See SRC ACP
- action congestion points 1
- configuring
- monitoring
- address pools. See IP address pools
- Admission Control Plug-In. See SRC ACP
- agents See NIC agents
- allocating bandwidth to applications not controlled by SRC ACP
- APIs
- APIs (application programming interfaces)
- application programming interfaces. See APIs
- applications
- executing with SRC ACP
- external for use with SRC ACP 1, 2
- assigned IP subscribers
- third-party devices 1
- assigning
- ATM access network, using with SRC ACP
- attributes
- authentication plug-ins
- authentication target
- configuration
- authorizing and tracking services
B
- backbone congestion point profiles
- backbone congestion points 1
- backbone network
- backbone network management with SRC ACP
- background bandwidth
- bandwidth
- allocating to applications not controlled by SRC ACP
- background 1, 2
- configuring
- for services 1, 2
- for subscribers
- downstream
- upstream
- bandwidths and congestion points for subscribers
- basic group
- BEEP, devices running Junos OS 1
- configuring port
- BEEP, Devices running Junos OS
- Blocks Extensible Exchange Protocol. See BEEP
C
- certificate authority (CA)
- classification scripts
- congestion point classification
- configuring
- criteria 1, 2
- description
- how it works
- targets 1, 2
- clients
- gateway
- Common Object Request Broker Architecture. See CORBA
- community manager
- configuring, third-party devices
- component interactions
- configuration group, devices running Junos OS 1, 2
- configuration manager, instantiating for NIC
- congestion point applications
- congestion point classification 1, 2
- congestion point classification scripts. See classification scripts
- congestion point expressions 1, 2
- congestion point profiles 1
- congestion points 1, 2
- congestion points by IP address and associated service sessions
- monitoring
- congestion points by login name and associated service sessions
- monitoring
- congestion points by session ID and associated service sessions
- monitoring
- conventions
- COPS (Common Open Policy Service)
- connection with JunosE routers 1
- COPS-PR versus COPS XDR
- JunosE router connection
- CORBA (Common Object Request Broker Architecture)
- CORBA interfaces
- CORBA-based plug-in SPI. See plug-ins, external
- customer support 1
- customized interface modules
D
- database accounting method
- configuration
- deriving congestion points
- device drivers
- Gx
- Junos
- configuring, SRC CLI
- viewing state, C-Web interface
- viewing state, SRC CLI
- viewing statistics, C-Web interface 1, 2
- viewing statistics, SRC CLI 1, 2
- JunosE
- configuring, SRC CLI
- viewing state, SRC CLI
- viewing statistics, SRC CLI 1, 2
- devices running Junos OS
- Devices running Junos OS
- directory
- directory blacklist, deleting 1, 2
- distinguished name. See DN
- DMI
- DMI driver
- migrating
- DMI network device
- adding
- DMI, devices running Junos OS
- DN (distinguished name)
- DNs
- documentation
- domain maps
- downstream bandwidth
- downstream RADIUS network elements and accounting targets
- configuration statements
- downstream RADIUS network elements and authentication targets
- configuration statements
E
- edge congestion points
- assigning to subscribers
- deriving
- DNs of
- monitoring
- edge network 1, 2
- edge network management, configuring
- equipment registration
- event notification, PCMM network
- configuration statements
- properties, configuring
- event notification, third-party devices
- events, publishing
- external applications
- external plug-ins
- external plug-ins. See plug-ins
- External Subscriber Monitor
- acting as pseudo RADIUS server, C-Web interface
- agent process statistics, viewing
- configuring
- configuring basic local properties
- configuring client secret
- configuring directory connection properties
- configuring event notification
- configuring eventing properties
- configuring initial properties
- configuring logging destinations
- event notifications, monitoring
- event notifications, viewing
- IP address manager 1
- overview, C-Web interface
- starting
- statistics, monitoring
- statistics, viewing
- stopping
F
- failover parameters, SAE 1, 2
- fault recovery, SRC ACP
- files
G
- group
- creation
- groups, NIC hosts
- Gx router driver
- adding router acting as PCEF
- charging rule installation
- charging rule removal
- charging rule report
- Charging-Rule-Install
- Gx router driver, configuring
- overview
- SAE
- SAE (service activation engine)
- SAE plug-ins
- service accounting
- session creation
- session detach
- session reauthorization
- session updation
- viewing state, SRC CLI
H
- hosted internal plug-in
- hosted plug-ins. See plug-ins
I
- interactions between SRC ACP and other components 1, 2
- interface classification scripts
- interface modules, SAE
- interfaces, assigning to backbone congestion point profiles
- internal plug-ins. See plug-ins
- IOR
- IP address pools
- IP pools
J
- JunosE routers
- accessing router CLI
- COPS connection 1
- integration overview
- monitoring interactions with SAE
- router objects, adding
- SRC client 1
- troubleshooting
- VR objects
- adding individually, SRC CLI 1, 2
- discovering, SRC CLI
L
- LDAP access. See SAE (service activation engine), configuring
- local properties
- configuration
- logging properties
- login names
- login process
- login registration
M
- managing
- manuals
- methods
- modifying congestion points
- monitoring
N
- NAS port ID
- network devices
- SNMP communities, configuring
- network information collector. See NIC
- network interfaces 1, 2
- network publisher See NIC
- NIC (network information collector) 1, See also other NIC entries
- API
- configuration prerequisites
- configuration statements
- configuration, changing
- configuration, verifying
- data mapping
- default operating properties, viewing
- factory interface 1, 2
- logging
- monitors
- network publisher
- operating properties, changing
- overview
- planning implementation
- realms
- replication
- replication, configuring
- resolution processes 1, 2
- resolvers
- restarting
- results
- roles
- starting
- stopping
- testing
- viewing
- NIC agents
- configuration overview
- directory, configuring
- overview 1, 2
- restarting
- sae client agents, configuring
- sae plug-in agents, configuring
- NIC configuration scenarios
- changing 1
- MultiPop
- OnePop
- OnePopAcctId
- OnePopAllRealms
- OnePopDnSharedIp
- OnePopDynamicIp
- OnePopLogin
- OnePopLoginPull
- OnePopPcmm
- OnePopPrefixIp
- OnePopPrimaryUser
- OnePopSharedIp
- OnePopStaticRouteIp 1, 2
- OnePopTunnel
- OnePopVrfIp 1, 2
- overview 1, 2
- scenario-name
- NIC hosts
- NIC locators
- NIC proxies
- cache, configuring
- configuration overview
- configuration prerequisites
- instantiating
- logging
- NIC replication, configuring
- overview
- prerequisites
- removing instances
- requirements 1, 2
- resolution information, configuring
- resolution requests
- NIC Proxy for Pseudo-RADIUS server
- NIC proxy for Pseudo-RADIUS server
- NIC resolvers
- nic-network-publisher-configuration-statements
- notice icons
O
- operation
P
- PacketCable Multimedia. See PCMM
- PCMM (PacketCable Multimedia)
- plug-ins
- preventing
- priorityList
- properties
- proxy RADIUS accounting method
- configuration
- pseudo-RADIUS server
- publishing events
R
- RADIUS accounting listener
- RADIUS accounting listener queue limits
- configuration
- RADIUS accounting listener transport
- configuration
- RADIUS authentication listener queue limits
- configuration
- RADIUS authentication listener transport
- configuring
- randomPick
- realm
- See NIC realms
- redundancy, SRC ACP
- rendering
- resolution processes
- roles, NIC
- roundRobin
- router initialization scripts
- router object
- adding for third-party devices
- routers
- accessing router CLI
- adding devices running Junos OS
- adding JunosE
- configuring SAE to communicate with Junos Space
- integrating devices running Junos OS 1, 2, 3
- integrating JunosE
- SNMP communities, configuring
S
- SAE (service activation engine)
- accounting
- APIs. See APIs
- BEEP connection, devices running Junos OS
- COPS
- deleting directory blacklist 1, 2
- device running Junos OS client
- Diameter connection, devices running Junos OS
- disabling interactions with device running Junos OS
- enabling interactions with device running Junos OS
- failover parameters 1, 2
- Gx router driver
- monitoring interactions
- NIC replication, configuring
- overview
- PCMM environment
- plug-ins See plug-ins
- reloading configuration 1, 2, 3, 4
- role
- router initialization scripts. See router initialization scripts
- session store
- starting
- stopping
- SAE (service activation engine), configuring
- BEEP connection
- COPS connection
- directory eventing, SAE configuration data
- event notification API properties
- LDAP access, SRC CLI
- router initialization script location
- serialized data compression
- session job manager
- session store
- SRC ACP
- SAE (service activation engine),configuring
- SAE communities
- configuring, third-party devices
- description, third-party devices
- SAE remote interface
- script services
- serialized data compression, configuring
- service activation engine. See SAE
- services
- configuring bandwidth for 1, 2
- monitoring
- preventing activation
- reloading on SAE 1, 2
- session job manager, configuring
- session state registrar See SSR
- session store
- SIC
- SIC (subscriber information collector)
- accounting listener
- accounting methods
- authentication methods
- configuring basic SIC group
- database accounting method
- default attributes in tagged attribute group, configuring
- device capabilities, configuring
- device models
- device models, configuration
- device templates, configuring
- Diameter server
- Diameter server identity, configuring
- Diameter server peer, configuring
- Diameter server, configuring
- dictionaries
- dictionaries, configuration
- downstream network element
- dynamic authorization
- how the process works
- overview 1, 2, 3
- editing rules
- editing rules, configuration
- editing rules, configuration statements
- event logging
- event logging, configuration
- explicit authentication routing, configuration statements
- explicit routing rules
- explicit routing, configuration
- explicit routing, configuration statements
- failover mode
- failover policy
- global service template default attributes, configuring
- global service template mode, configuring
- global service template normal attributes, configuring
- global service template override attributes, configuring
- global service template parameterized attributes, configuring
- global service template required attributes, configuring
- global service template variables, configuring
- global service templates, configuring
- global service templates, creating
- global service templates, overview
- implicit routing rules
- implicit routing, configuration
- local and shared configuration
- local realms
- local realms, configuration
- normal attributes in tagged attribute group, configuring
- override attributes in tagged attribute group, configuring
- overview
- parameterized attributes in tagged attribute group, configuring
- primary/backup
- proxy accounting method
- proxy function
- RADIUS configuration
- RADIUS transport for server, configuring
- RADIUS transports
- request routing rules
- request routing, configuring
- required attributes in tagged attribute group, configuring
- round robin
- server instance, creation
- service template default attributes, configuring
- service template mode, configuring
- service template normal attributes, configuring
- service template override attributes, configuring
- service template parameterized attributes, configuring
- service template required attributes, configuring
- service template samples
- service template variables, configuring
- service template, configuration statements
- service template, tagged attribute configuration statements
- service templates, configuring
- service templates, creating
- service templates, overview
- SNMP support
- snmp, configuring
- statistics
- tagged attribute group, creating
- tagged attributes in, configuring
- upstream network element
- SIC accounting and authentication clients
- configuring
- SIC accounting and authentication targets
- configuring
- SIC accounting targets
- configuring
- SIC authentication targets
- configuring
- SIC dynamic authorization targets
- configuring
- SIC upstream and downstream network elements
- SNMP
- SNMP communities
- configuring
- SOAP
- Soap Fault Codes
- VTA
- SRC ACP (SRC Admission Control Plug-In) 1
- API
- ATM access network
- authorizing and tracking services
- backbone network management, configuring
- classification scripts
- configuring
- congestion points
- connections to services directory, configuring
- connections to subscribers’ directory, configuring
- CORBA interfaces, configuring
- data files
- data files, reorganizing
- description of
- event publishers, configuring
- external applications 1, 2
- external plug-in for SAE, configuring
- fault recovery
- groups, configuring 1, 2
- information from external applications, displaying
- interactions with other components
- logging properties, configuring
- monitoring
- operation, configuring
- preventing service activation
- properties
- redundancy 1
- SAE, configuring for
- starting
- state synchronization 1
- stopping
- subscribers, monitoring 1, 2
- supporting multiple SAEs
- using multiple SRC ACPs
- SRC ACP (SRC Admission Control Plug-In), congestion points
- SRC Admission Control Plug-In. See SRC ACP
- SRC client, JunosE routers
- SRC software process, Devices running Junos OS
- SRC software process, devices running Junos OS 1, 2
- SRC Volume Tracking Application
- SRC Volume-Tracking Application SRC Volume-Tracking Application See SRC VTA
- SOAP interface
- SRC Volume-Tracking Application (SRC VTA)
- account and session database connection, configuring See SRC CLI
- database deadlocks
- database to store account and session data, configuring See SRC CLI
- db-engine processor
- group, configuring See SRC CLI
- JDBC .jar file See installing
- keys to specify subscriber-id-solution See SRC CLI
- tracking events
- SRC Volume-Tracking Application (VTA)
- group
- SRC Volume-Tracking Application. See SRC VTA
- SRC VTA
- accounts and service sessions
- balance change history records
- events
- performance statistics
- session history records
- sessions
- SOAP API statistics
- subscriber accounts
- subscriber balance changes
- subscriber session history
- testing configuration
- SRC VTA (SRC Volume-Tracking Application (SRC VTA)
- SRC VTA (SRC Volume-Tracking Application)
- account and session database connection, configuration
- accounts
- description
- interim accounting interval, setting
- service
- subscriber
- usage metric, setting 1, 2, 3
- actions 1
- architecture
- bought account
- bought quota 1
- connections to SRC components
- database
- database engine processor
- db-engine processor
- e-mail notifications, sending
- event attributes
- event handlers
- event queue
- events 1
- example
- functions
- group, configuring
- how it works
- initial account balance
- initial account status
- interval accounting interval, setting 1, 2
- JavaScript programs
- keys to specify subscriber-id-solution
- logging events to a text file
- mail processor
- on-error
- operation process
- overview
- periodic account
- periodic quota 1
- processors
- providing volume-based services
- quota service 1
- related configuration tasks
- SAE events
- saving event messages on a system logging server
- script runner processor
- scripts
- external 1, 2
- JavaScript programs
- services
- sessions
- subscriber login with IP address
- types
- usage metric, configuring 1, 2, 3
- SRC VTA (Volume-Tracking Application)
- actions
- database deadlocks
- event handlers
- function
- on-error
- related configuration tasks
- SSR (session state registrar)
- adding a client node to an active cluster
- adding a management server to a client node in an active cluster
- adding data nodes to an active cluster
- attribute associations, configuring in an active cluster
- cluster configurations
- cluster network requirements
- cluster status, viewing
- configuration statements
- configuring
- cluster name
- cluster nodes
- database memory size
- geometry
- initial cluster
- management server
- subscriber sessions schema 1, 2
- creating
- database memory requirements, viewing
- database mode, viewing
- database modes
- database schema
- database schema, configuring in an active cluster
- database, viewing running configuration
- deleting
- disabling
- distributing the cluster configuration
- enabling
- impact of configuration changes
- making modifications to subscriber sessions table
- node groups
- node types
- overview
- placing
- planning the cluster topology
- planning worksheets
- removing
- restarting
- scaling the cluster
- server requirements
- supported configurations
- viewing, all subscriber sessions
- viewing, subscriber sessions by indexed field
- viewing, subscriber sessions by IP address
- viewing, total number of subscriber sessions
- starting
- state synchronization
- statistics, SRC ACP
- stopping SRC ACP
- subscriber information collector subscriber information collector See SIC
- authentication target, configuring
- basic group, configuring
- configuration summary
- configuring management of RADIUS-enabled devices for the SIC
- database accounting method, configuring
- default attributes in tagged attribute group, configuring See SIC
- device capabilities, configuring See SIC
- device models, configuring See SIC
- device templates, configuring See SIC
- Diameter configuration summary
- Diameter server See statements
- Diameter server identity, configuring See SIC
- Diameter server peer, configuring See SIC
- Diameter server, configuring See SIC
- dictionaries, configuring See SIC
- dynamic authorization
- editing rules, configuration statements See SIC
- editing rules, configuring See SIC
- event logging, configuring See SIC
- explicit authentication routing, configuration statements See SIC
- explicit routing, configuration statements See SIC
- explicit routing, configuring See SIC
- global service template default attributes, configuring See SIC
- global service template mode, configuring See SIC
- global service template normal attributes, configuring See SIC
- global service template override attributes, configuring See SIC
- global service template parameterized attributes, configuring See SIC
- global service template required attributes, configuring See SIC
- global service template variables, configuring See SIC
- global service templates, configuring See SIC
- global service templates, creating See SIC
- global service templates, overview See SIC
- group, creating
- implicit routing, configuring See SIC
- local properties
- local realms, configuring See SIC
- normal attributes in tagged attribute group, configuring See SIC
- outbound RADIUS transport for group, configuring See SIC
- override attributes in tagged attribute group, configuring See SIC
- parameterized attributes in tagged attribute group, configuring See SIC
- proxy RADIUS accounting method, configuring
- RADIUS accounting listener queue limits, configuring
- RADIUS accounting listener transport, configuring
- RADIUS accounting listener, configuring 1, 2
- RADIUS authentication listener queue limits, configuring
- RADIUS authentication listener transport, configuring
- RADIUS configuration summary
- RADIUS dynamic authorization configuration summary
- RADIUS transport for server, configuring See SIC
- request routing, configuring See SIC
- required attributes in tagged attribute group, configuring See SIC
- server instance, creating See SIC
- service template default attributes, configuring See SIC
- service template mode, configuring See SIC
- service template normal attributes, configuring See SIC
- service template override attributes, configuring See SIC
- service template parameterized attributes, configuring See SIC
- service template required attributes, configuring See SIC
- service template samples See SIC
- service template variables, configuring See SIC
- service template, configuration statements
- service template, tagged attribute configuration statements
- service templates, configuring See SIC
- service templates, creating See SIC
- service templates, overview See SIC
- snmp, configuring See SIC
- tagged attribute group, creating See SIC
- tagged attributes in service templates, configuring See SIC
- subscriber information collector (SIC)
- accounting and authentication clients
- accounting and authentication targets
- accounting targets
- authentication targets
- device models in network element
- dynamic authorization targets
- failover mode
- failover mode and policy
- fast fail options for the failover policy
- retry options for the failover policy
- upstream and downstream network elements
- subscribers
- assigning interfaces to
- configuring bandwidths and congestion points for 1, 2
- IP addresses
- login names
- monitoring
- provisioned and actual bandwidths
- subscriptions
- support, technical See technical support
T
- targets. See classification scripts
- technical support
- text conventions defined
- third-party devices
- creating sessions
- integrating into SRC network
- logging in subscribers
- provisioning with script services
- router objects, adding
- SAE communities
- VR objects, adding
- threads
- configuring for sessions
- tracking plug-ins
- troubleshooting
- tuning factors for background bandwidth
U
- upstream bandwidth
- upstream network elements, accounting and authentication clients, and dynamic authorization targets
V
- virtual routers
- Volume-Tracking Application (VTA)
- VTA See SRC VTA
- VTA (SRC Volume-Tracking Application)
- accounts
- event attributes
- event handlers 1
- event queue
- events
- SAEEventListener
- sessions
- VTA (Volume-Tracking Application)
- database to store account and session data, configuration
- prerequisites for running
- tracking events
W
- Web application server
- application deployment
- channel stack
- configuration statements
- configuring the Web application server
- installing Web applications inside
- local properties
- multicast-address
- node-id
- shared cluster name
- shared cluster nodes
- shared cluster properties
- starting
- Web Services Definition Language. See WSDL
- Web Services Gateway
- clients
- WSDL files
Download This Guide
SAE Accounting
The router and the SAE generate RADIUS accounting records when subscribers access the Internet and use value-added services. The records are sent to RADIUS accounting servers and are logged in accounting log files, or they are sent to accounting flat files. External systems collect the accounting log files and feed them to a rating and billing system.
The SRC module allows a variety of accounting deployments. This topic shows the standard deployment that we supply, a second option that does not depend on a RADIUS server, and a third option in which customers develop their own deployment by choosing a CORBA plug-in.
In the standard SRC deployment (see Figure 4), the router and the SAE are clients of the RADIUS accounting server. They pass subscriber accounting information to a designated RADIUS accounting server in an accounting request. The RADIUS accounting server receives the accounting request and creates accounting log files.
The SRC module works with other AAA RADIUS servers; however, we validate the SRC module only with Merit, Interlink RAD-Series AAA RADIUS Server, or Juniper Networks Steel-Belted Radius/SPE server.
Figure 4: Sending Accounting Data to a RADIUS Server

A second option, shown in Figure 5, uses an accounting flat file generated directly by the SAE, without a RADIUS server.
Figure 5: Sending Accounting Data to an Accounting File

Figure 6 illustrates a third possibility, one in which the customers use a CORBA plug-in of their own choice.
Figure 6: Customer Choice for SRC Accounting Deployment

Accounting Policy
The SAE defines the policies that control the network traffic for the subscriber based on the subscriber’s subscriptions. It also determines the accounting statistics collected for the subscribed service.
While defining the policies for a service, the SAE can choose the policy rules to be used for accounting per interface direction (ingress and egress). Statistics are collected for the chosen policy rules for the service and are sent to the RADIUS accounting server. The SAE can also decide not to collect any policy rule–specific statistics for the service. In this case, only session times are sent to the accounting system when the service is deactivated. When choosing multiple policy rules on traffic direction for statistics collection, the SAE summarizes the statistics by adding the individual values.
The SRC software allows you to enable or disable the accounting-per-attachment feature to calculate accounting for each individual policy list on the basis of the accounting flag status of each policy rule in the policy list. This capability optimizes the creation of statistics for the policy list. When the accounting-per-attachment feature is enabled for a policy list, accounting statistics are calculated per policy list only if the accounting flag is enabled on any one of the policy rules in that policy list. If the accounting flag of all policy rules in the policy list is disabled, the accounting statistics are not calculated for all policy lists even though the accounting-per-attachment feature is enabled. When the accounting-per-attachment feature is disabled for a policy list, accounting statistics are not calculated per policy list irrespective of the accounting flag status of all policy rules in that policy list. By default, the accounting-per-attachment feature is not set. If the accounting-per-attachment feature is not configured, the accounting statistics are calculated for all policy lists irrespective of the accounting flag status of all policy rules in that policy list.
![]() | Note: The accounting-per-attachment feature is supported only on E Series routers. |
Any change in the enabling or disabling of the accounting-per-attachment feature takes effect only after the sscc connection is restarted. After you restart the sscc connection, accounting statistics are calculated for the updated policy list on the basis of the configuration of the accounting-per-attachment feature. Accounting statistics are calculated when the policy list is attached to an interface or subscriber.
When the attached policy list is changed, the SRC software sends a new policy attachment message containing the recalculated accounting-per-attachment statistics flag to the subscriber who uses the policy list. If the policy list is shared by subscribers, then the SRC software sends a new policy attachment message containing the recalculated accounting-per-attachment statistics flag to all subscribers who use the policy list. The policy list attached to the interface or subscriber can be changed for the following reasons:
- Policy structure change made by the administrator
- Activation or deactivation of manual services
Table 4 lists cases for the collection of various accounting information based on the accounting-per-attachment feature for previous policy lists attached to the interface or subscriber.
Table 4: Accounting Information Collection Based on the Accounting-Per-Attachment Feature for Previous Policy Lists
Accounting-Per-Attachment Feature for Previous Policy List | Final Accounting Information Collection | Policy Change Accounting Information Collection |
---|---|---|
Enabled | Information is collected from the router when the policy list attached to the interface or subscriber is changed. | Information for the previous policy is received from the router when the new policy is attached for the interface or subscriber. |
Disabled | Information is not collected from the router when the policy list attached to the interface or subscriber is changed. | Information for the previous policy is not received from the router when the new policy is attached for the interface or subscriber. |
Null | Information is collected from the router when the policy list attached to the interface or subscriber is changed. | Information for the previous policy is received from the router when the new policy is attached for the interface or subscriber. |
Table 5 lists cases for the collection of various accounting information based on the accounting-per-attachment feature.
Table 5: Accounting Information Collection Based on the Accounting-Per-Attachment Feature
Accounting-Per-Attachment Feature | Interim Accounting Information Collection | Rule-Level Accounting Information Collection |
---|---|---|
Enabled | Information is collected from the router for the interface or subscriber. | Information is collected from the router for a policy rule if the accounting flag for that rule is enabled. Otherwise, information is not collected from the router. |
Disabled | Information is not collected from the router for the interface or subscriber. | Information is not collected from the router for a policy rule. |
Null | Information is collected from the router for the interface or subscriber. | Information is collected from the router for a policy rule. |
Subscription Process
After an outsourced service has been set up, subscribers can order primary access or value-added services from retailers, who in turn notify the wholesaler of the new end subscription. Conversely, accounting data is collected by the wholesaler and communicated to the retailer to provide enough data for the retailer to bill the subscriber.
The overall subscription process is simplified:
- The subscriber has no need to interact with another party or a device other than the router.
- When the subscriber goes to the Web portal and selects the service, the subscription activation is triggered.
- The subscriber’s portal page adjusts to display the new service.
- Accounting data is generated, identifying the service being tracked for the subscriber.
Tracking Subscriber Sessions
The intelligent service accounting function of the SRC module tracks the subscription activity for each subscriber and each service session. It collects usage information and passes the information to the appropriate rating and billing system.
Multiple service sessions can be activated simultaneously for a subscriber and can be tracked separately from an accounting standpoint.
Events are generated when service sessions are activated and deactivated, and during interim accounting updates.
Accounting Plug-Ins
Plug-ins allow service providers to easily extend the capabilities of their systems through the use of plug-in software. See SAE Plug-Ins.
Interim Accounting
The router and SAE generate interim accounting records for broadband primary services (through PPP) and value-added services, respectively. RADIUS servers log the interim records in their accounting log files when interim accounting is enabled.
The external rating system calculates the charges by using interim records instead of stop records for timeout sessions. The calculation occurs when the last record is interim and for open sessions whose last record at the end of a billing cycle is interim.
An accounting interim interval is defined for each service and applied to all subscriptions to that service. The router and SAE generate accounting requests with a status of interim for every period of time specified with the interim value.
The router receives an accounting interim value for a session through a RADIUS server when the router makes an authentication request. If the RADIUS server does not provide a value, then the router does not generate interim accounting records.
The SAE obtains an accounting interim value from the directory. When the accounting interim value is not stored, the SAE uses global values. When a value equals zero, the SAE does not generate interim accounting records.
Related Documentation
- Role of the SAE
- Connections to Managed Devices
- SAE Plug-Ins
- Tracking and Controlling Subscriber and Service Sessions with SAE APIs
- Adding Routers Individually (SRC CLI)
- Configuring the SAE to Manage JunosE Routers (SRC CLI)