Juniper Networks SRC Series
Session and Resource Control Software

Architecture and Key Components:

SRC Series Software

The SRC Series advanced software consists of:

• The SRC Policy Engine (SRC PE), which maintains a directory of customer, network, and service configuration information that it uses to enable automated, policybased service and subscriber provisioning. The SRC PE also allocates network resources in response to subscriber and application requests, to ensure quality of service (QoS) and quality of experience (QoE) and to protect the quality of previously accepted sessions. It collects usage information on a per-subscriber or perservice basis in order to implement usage-based billing, fair usage, or reporting. The SRC-PE integrates with a variety of Juniper products, including MX Series and E Series platforms, as well as third party network elements, leveraging protocols such as Diameter, COPS-PR, RADIUS/ CoA, XML, and scripting.
• The SRC Diameter Gateway (SRC DG), which provides a Diameter interface that enables the SRC PE to perform Access Resource and Admission Control Functions (A-RACF), and to provision policies for Session Initiation Protocol (SIP) services, across the IP/MPLS network infrastructure.
• 3GPP-Gateway: SRC Series software can interface with third-party PCRFs leveraging 3GPP Gx reference point. In this architecture, the SRC Series can mediate between PCRF and non-3GPP compliant devices.
• IMS-Gateway: SRC Series software can perform Access Resource and Admission Control Functions (A-RACF), integrating with SPDF over Rq reference interface. The SRC Series provides network resource management and dynamic policies for multimedia services.
• The SRC SOAP Gateway (SRC SG), which uses the SOAP Protocol to provide a simple, straightforward, and standards-based interface that allows non-SRC Series applications to integrate with, and make use of, SRC Series software.
• The SRC Volume Tracking Application (SRC VTA), which tracks subscribers, sessions, and applications based on granular, customer configurable thresholds for volumes and durations, enabling fair resource usage. The SRC VTA supports tiered service offerings and can invoke policydriven actions based on predefined thresholds, including rate limiting of traffic, activation of additional resources, and removal of abusive users.

Features & Benefits:

Features	Advantages	Benefits
Prepackaged solution	Easy to dimension, test, install, configure, upgrade, troubleshoot, and spare	Simplifies the operating environment
Intelligent call admission control	Considers multiple criteria (subscriber privileges, service profile, application requirements, network availability) to make per-session admission control decisions	Ensures high service quality for requested and preexisting sessions, and provides subscriber QoE
Service-level accounting	Tracks and accounts for dynamically initiated services for OSS/BSS handof	Supports unique service models
Flexible service activation	Provides identity-based, application-based, and subscriber self-service selection	Provides mass service customization, stronger customer relationships, and competitive differentiation without increasing operating complexity or costs
Open interfaces	Integrates with third-party network elements and applications to enable end-to-end, application-driven network resource control	Enables application-driven resource control over multivendor networks
Subscriber self-provisioning and service creation tools	Provides policy-driven subscriber and service automation at carrier scale	Enables decreased time to market and reduced costs to roll out new services
Virtualized software (vSRC)	Takes advantage of commonly available offthe-shelf hardware.	Provides flexibility to customize and expand based on need and current conditions.

Use Cases:

The SRC Series Session and Resource Control Software supports a suite of applications that enable the creation of myriad services limited only by the creativity of service providers, system integrators, and the enterprise. Several examples are described here.

Multiplay Services: Assured Video

When a subscriber requests a video service (A), the video server notifies the SRC Policy Engine via the SRC SOAP Gateway (B). The SRC Policy Engine monitors the network (C) to determine whether adequate resources are available to support the request. If the resources exist, the SRC Policy Engine reserves them (C) and notifies the video server to initiate the service (B); if sufficient resources are not available, the SRC Policy Engine can resize existing LSPs or create new ones to handle the additional traffic, or gracefully reject the request and notify the subscriber, depending on the service provider’s defined policy. The SRC Policy Engine also dynamically rate-limits other services that the subscriber may concurrently consume to assure high video QoE.

Multiplay Services: Assured Voice

In this example, the service provider has implemented a multiplay network that supports both IMS and non-IMS services over a converged infrastructure. The policy and control solution consists of the SRC Policy Engine, the SRC SOAP Gateway, and the SRC Diameter Gateway, in addition to OSCP partner products. Video and data applications communicate with the SRC Policy Engine via the SRC SOAP Gateway (A), and voice over IP (VoIP) service requests are conveyed to the SRC Policy Engine by a Session Border Controller via the SRC Diameter Gateway (B). The SRC Policy Engine provides traffic engineering for VoIP and video sessions based on real-time LSP awareness and can allocate, resize, and create network resources in response to application requirements (C). The sessions are gracefully rejected if sufficient resources are unavailable.

Tiered Access Services and Subscriber Self-Provisioning

In this example, the service provider uses the SRC Policy Engine with the built-in, selfservice portal, the SRC SOAP Gateway, and the SRC Volume Tracking Application to offer tiered subscriber selectable service packages based on traffic volume, connection speed, and duration. Subscribers use the selfservice portal (A) to make a service selection that the SRC Policy Engine configures on the network (B). A partner application monitoring the xDSL train rate is integrated into the solution via the SRC SOAP Gateway (C). Changes in the train rate trigger the SRC Policy Engine to make changes to the subscriber’s service profile. The SRC Volume Tracking Application monitors and accounts for subscriber use, and this accounting information is also provided to OSS/BSS accounting, billing, and customer care systems (D).

Technical Specifications:

CPU Requirements:

• You must allocate at least one CPU core for virtualized SRC Series software. For comparison purposes, here are the equivalent CPU characteristics of previously available C Series hardware:
  • C2000: 4
  • C3000: 8
  • C5000: 24

Storage:

• The qcow2 image and vmdk image (of subtype monolithicSparse) grow in size up to 250 GB when used on a virtual machine, so there must be more than 250 GB of disk space available in the host operating system to use the qcow2 or vmdk image. If using an SRC Series iso image, it is recommended that 250 GB of disk space be allocated to the virtualized SRC Series software to ensure enough space is available for system and component logs.

Network

• 1GbE or 10GbE interface card (one or more)

Hypervisors

• VMware, Centos 6.5 KVM

Image Formats:

• qcow2
• iso
• vmdk
• img (for installation on legacy C Series C3000 and C5000 hardware)

SRC Component	Default Heap Size for vSRC	Heap Size Adjustable	Stack Size
ACP	64 MB	Yes	1024 KB
SNMP agent	160 MB	No	1024 KB
Web application server	616 MB	No	1024 KB
CLI	200 MB	No	1024 KB
Diameter server	600 MB	No	1024 KB
External subscriber monitor	160 MB	Yes	1024 KB
3GPP gateway	200 MB	No	1024 KB
IMS services gateway	200 MB	No	1024 KB
JPS	400 MB	Yes	1024 KB
License server	1 GB or less than ¼ of physical memory	No	1024 KB
NIC	128 MB	Yes	1024 KB
SAE	70% of free memory	Yes	228 KB
C-Web interface	200 MB	No	1024 KB

Documentation:

Download the Juniper Networks SRC Series Datasheet (PDF).