Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Release Highlights

Highlights include the following product enhancements:

Note: The SRC software runs as VMs and runs on C Series Controllers—a range of hardware platforms. The SRC 4.9.0 software contains the features found in the SRC 4.8.0 release plus the features listed in this section. The SRC 4.9.0 software may contain references to the service activation engine (SAE) Release version 7.15.0. SRC 4.9.0 software does not run on the discontinued C2000 and C4000 controllers because of hardware incompatibility.

Southbound Gx Interface Support to Manage MX Series Router (Services Control Gateway) Acting as PCEF

The SRC software now includes a Gx router driver to establish a southbound Gx interface between the MX Series router (that is, Services Control Gateway) acting as a PCEF and the SRC software acting as a PCRF. The SRC software performs the following actions:

  • Provides solicited and unsolicited provisioning of PCC or ePCC rules to the Services Control Gateway.
  • Removes the provisioned PCC or ePCC rules.
  • Detects and controls traffic of the Services Control Gateway.
  • Monitors service usage for the subscriber.
  • Sends Diameter messages to activate the rules predefined on the Services Control Gateway.

The SRC software uses the CCA and RAR messages to communicate with the Services Control Gateway over the southbound Gx interface. The SRC software supports specific attributes mentioned in the 3GPP TS 29.212 specification to implement this feature. You can configure the supported attributes by defining static PCC rules, dynamic PCC rules, or dynamic ePCC rules. You can also configure some 3GPP attributes at service level and subscriber level through newly introduced CLI commands.

The outputs of the show commands displaying SAE driver details, SAE subscriber information, and Diameter statistics are enhanced to display the message statistics and 3GPP attributes details for the Gx router driver.

The routerConnUp and routerConnDown traps are now enhanced to notify the SAE when the Gx router driver is in operational state or in unconnected state.

New plug-in attributes are introduced in the SRC software to publish usage monitoring information and detected application information related to the Services Control Gateway.

The SRC software does not currently support interim accounting interval functionality, time and money based usage monitoring functionality, dual stack functionality for Services Control Gateway, and time of day procedure.

Northbound Gy Interface Support to Handle Charging-Related Information

A new component, 3GPP Gy, is introduced in the SRC software to provide Gy-based integration with the OCS. SRC’s Gy uses a 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. SRC’s Gy issues corresponding requests to the OCS on receiving a service authorization, service stop, or service tracking event from the SAE. Based on the response received from the OCS, SRC’s Gy requests the SAE to activate or not to activate the service for the subscriber.

The SRC software enables you to define multiple OCSes. In this case, SRC’s Gy selects the active peer among the defined OCSes and interacts with the active peer. If the active peer fails, SRC’s Gy selects another active peer. SRC’s Gy does not switch back to the original active peer when it comes online.

The SRC software enables you to define multiple instances of SRC’s Gy pointing to the same namespace in the shared configuration to handle communication between the same group of SAEs and OCSes. In this case, all instances of the same namespace use a community manager to elect an active member to handle communication between the SAE and OCS. If the active member fails, the community manager elects another active member.

SRC’s Gy always assumes that the service identifier and subscription identifier are in synchronization between the SRC software and OCS. SRC’s Gy sends a separate request message to the OCS for each services and supports only service identifier based credit control messages.

SRC’s Gy does not currently support time-based quota, money-based quota, service specific units, unit determination functionality, rating functionality, quota holding time functionality for volume-based quota, quota consumption time functionality for volume-based quota, traffic time change functionality, rating group functionality, and redirection for final unit indication.

SRC Virtualization Support

The SRC software can now be deployed as a VM either using an iso image or qcow2 image. All SRC functionalities are supported on the virtualized SRC software except the following:

  • Hardware-specific commands such as show disk status
  • Hardware-related alarm or traps such as diskFailure
  • IPMI-related commands

We recommend you to create a virtualized SRC instance by using the qcow2 image. You must ensure that enough system resources (similar to that of C series controller) are allocated to the virtualized SRC software for better management and support of SRC functionalities.

The SRC software installation is currently tested and supported only over the KVM hypervisor on CentOS 6.5. The SRC software does not have any hypervisor management tool.

Modified: 2015-11-30