Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

SRC Component Overview

 

The SRC software is a dynamic system. It contains many components that you use to build a subscriber management environment. You can use these tools to customize and extend the SRC software for your use and to integrate the SRC software with other systems. The SRC software also provides the operating system and management tools for C Series Controllers.

Table 4 gives a brief description of the components that make up the SRC software.

Table 4: Descriptions of SRC Components

Component



Description



Server Components

Service activation engine (SAE)

  • Authorizes, activates, and deactivates subscriber and service sessions by interacting with systems such as Juniper Networks routers, cable modem termination system (CMTS) devices, RADIUS servers, and directories.

  • Collects accounting information about subscribers and services from routers, and stores the information in RADIUS accounting servers, flat files, and other accounting databases.

  • Provides plug-ins and application programming interfaces (APIs) for starting and stopping subscriber and service sessions and for integrating with systems that authorize subscriber actions and track resource usage.

Subscriber Information Collector (SIC)

The SIC listens for RADIUS accounting events from IP edge devices (accounting clients) and forwards them to a remote AAA server, allowing the SRC software to gain increased subscriber awareness. Additionally, the SIC can optionally edit accounting events before routing them.

Network information collector (NIC)

Collects information about the state of the network and can provide a mapping from a given type of network data to another type of network data.

Redirect Server

Redirects HTTP requests received from IP Filter to a captive portal page.

3GPP Gateway

The SRC Third-Generation Partnership Project (3GPP) gateway is a Diameter-based component in the SRC software, which provides integration with 3GPP Policy and Charging Control environments, to provide fixed-mobile convergence (FMC). The SRC 3GPP gateway provides Gx-based integration with the Policy and Charging Rules Function (PCRF). The SRC 3GPP gateway uses the northbound Gx interface to mediate between the PCRF and Juniper Networks routers like the E Series Broadband Services routers and MX Series routers. The northbound Gx interface on the SRC 3GPP gateway communicates with the PCRF using the Diameter protocol.

3GPP Gy

The SRC 3GPP Gy is a Diameter-based component in the SRC software, which provides Gy-based integration with the Online Charging System (OCS), to provide FMC. The SRC 3GPP Gy uses the northbound Gy interface to handle charging-related information between the OCS and Juniper Networks routers like the E Series Broadband Services routers and MX Series routers. The northbound Gy interface communicates with the OCS using the Diameter protocol.

Web Application Service

The SRC software includes a Web application server that hosts the Web Services Gateway and the Volume Tracking Application (SRC VTA). In production environments, this application server is designed to host only these applications. However, you can load your own applications into this server for testing or demonstration purposes.

Web Services Gateway

Allows a gateway client—an application that is not part of the SRC network—to interact with SRC components through a Simple Object Access Protocol (SOAP) interface.

The Web Services Gateway provides the Dynamic Service Activator which allows a gateway client to dynamically activate and deactivate SRC services for subscribers and to run scripts that manage the SAE.

Monitor Components Connectivity (MCC)

Monitors the connectivity state between SAEs in a community and between SAE and RADIUS server periodically and collects diagnostic information about the connectivity state of components, such as connection error, connection timeout, and socket read/write timeout.

Repository

Directory

The SRC software includes the Juniper Networks database, which is a built-in Lightweight Directory Access Protocol (LDAP) directory for storing all SRC data including services, policies, and small subscriber databases.

For large subscriber databases, you must supply your own directory.

SRC Configuration and Management Tools

SRC command line interface (CLI)

Provides a way to configure the SRC software on a C Series Controller from a Junos OS–like CLI. The SRC CLI includes the policies, services, and subscribers CLI, which has separate access privileges.

C-Web interface

Provides a way to configure, monitor, and manage the SRC software on a C Series Controller through a Web browser. The C-Web interface includes a policies, services, and subscribers component, which has separate access privileges.

Simple Network Management Protocol (SNMP) agent

Monitors system performance and availability. It runs on all the SRC hosts and makes management information available through SNMP tables and sends notifications by means of SNMP traps.

Service Management Applications (Run on external system)

IMS Services Gateway

Integrates into an IP multimedia system (IMS) environment. The SRC software provides a Diameter protocol-based interface that allows the SRC software to integrate with services found on the application layer of IMS.

SRC Programming Interfaces

NETCONF API

Allows you to configure or request information from the NETCONF server on a C Series Controller that runs the SRC software. Applications developed with the NETCONF API run on a system other than a C Series Controller.

CORBA plug-in service provider interface (SPI)

Tracks sessions and enables linking the rest of the service provider’s operations support system (OSS) with the SRC software so that the OSS can be notified of events in the life cycle of SAE sessions. Hosted plug-ins only.

CORBA remote API

Provides remote access to the SAE core API. Applications that use these extensions to the SRC software run on a system other than a C Series Controller.

NIC access API

Performs NIC resolutions. Applications that use these extensions to the SRC software run on a system other than a C Series Controller.

SAE core API

Controls the behavior of the SRC software. Applications that use these extensions to the SRC software run on a system other than a C Series Controller.

Script services

Provides an interface to call scripts that supply custom services such as provisioning policies on a number of systems across a network.

 

VTA API

The Volume Tracking Application (VTA) API is a Simple Object Access Protocol (SOAP) interface that allows developers to create gateway clients and that administrators use to manage VTA subscribers and sessions. The SRC Web Services Gateway allows a gateway client—an application that is not part of the SRC network—to interact with SRC components, such as the VTA, through a SOAP interface.

Authorization and Accounting Applications

AAA RADIUS servers

Authenticates subscribers and authorizes their access to the requested system or service. Accepts accounting data—time active and volume of data sent—about subscriber and service sessions. RADIUS servers run on a system other than a C Series Controller.

SRC Admission Control Plug-In (SRC ACP)

Authorizes and tracks subscribers’ use of network resources associated with services that the SRC application manages.

Flat file accounting

Stores tracking data to accounting flat files that can be made available to external systems that send the data to a rating and billing system.

Volume Tracking Application

The SRC Volume Tracking Application (SRC VTA) is an SRC component that allows service providers to track and control the network usage of subscribers and services. You can control volume and time usage on a per-subscriber or per-service basis. This level of control means that service providers can offer tiered services that use volume as a metric, while also controlling abusive subscribers and applications.

When a subscriber or service exceeds bandwidth limits (or quotas), the SRC VTA can take actions including imposing rate limits on traffic, sending an e-mail notification, or charging extra for additional bandwidth consumed.

Demonstration Applications (available on the Juniper Networks Website)

Enterprise Audit Plug-In

Defines a callback interface, which receives events when IT managers complete specified operations.

Enterprise Manager Portal

Allows service providers to provision services for enterprise subscribers on routers running JunosE or Junos OS and allows IT managers to manage services.

Enterprise Manager Portal can be used with NAT Address Management Portal to allow service providers to manage public IP addresses for use with NAT services on routers running Junos OS and to all IT managers to make requests about public IP addresses through the Enterprise Manager Portal.

Monitoring Agent application

Integrates IP address managers, such as a DHCP server or a RADIUS server, into an SRC-managed network so that the SAE is notified about subscriber events. The Monitoring Agent application runs on a Solaris platform.

Residential service selection portals

Provides a framework for building Web applications that allow residential and enterprise subscribers to manage their own network services. It comes with several full-featured sample Web applications that are easy to customize and suitable for deployment. The Residential service selection portals run on a Solaris platform.

Sample enterprise service portal

Lets service providers supply an interface to their business customers for managing and provisioning services.