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 
ContentIndex
  
[+] Expand All
[-] Collapse All

Symbols  A  B  C  D  E  G  I  L  M  N  O  P  R  S  T  W

 

Symbols

3GPP    
Charging-Rule-Base-Name
gateway    
configuration example
3GPP gateway    
charging rule    
installation example
removal example
charging rule installation    
service activation
charging rule removal    
service deactivation
charging rule report
Charging-Rule-Base-Name
Charging-Rule-Install
Charging-Rule-Name
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
Gx interface    
configuring
initial properties    
configuring
Juniper-Substitution
Juniper-Substitution-Name
Juniper-Substitution-Value
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
non-parameterized charging rule
object adapter Internet address    
configuring
overview
parameterized charging rule
PCRF
peer communication    
redundancy
restarting
SAE    
mapping between concepts
service accounting
service activation sequence
service deactivation sequence
service modification sequence
session termination sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy    
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
initial properties    
configuring
interface    
configuring
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
object adapter Internet address    
configuring
overview
peer communication    
redundancy
restarting
service activation sequence
service deactivation sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy NIC proxies    
cache, configuring    
SRC CLI
NIC replication, configuring    
SRC CLI
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI
 

A

Application Services Gateway.     See Web Services Gateway    
arguments for scripts and methods
ASG (Application Services Gateway).     See Web Services Gateway    
 

B

B2B environments
business partner responsibilities    
Dynamic Service Activator
business partners
business-to-business environments
 

C

classify-traffic condition    
expanded classifiers    
configuring
clients    
gateway    
testing
Web Services Gateway
Web Services Gateway
configuration namespace
conventions    
notice icons
text
customer support    1
contacting JTAC
 

D

Diameter    
peers    
configuring    12
documentation    
comments on
dynamic properties
Dynamic Service Activator    
access constraints    
defining    12
access to attributes    
configuring, SRC CLI
access to methods    
configuring, C-Web interface
configuring, SRC CLI
access to methods and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
access to scripts    
configuring, C-Web interface
configuring, SRC CLI
access to service sessions    
configuring, SRC CLI
API
attributes    
access to
configuring with C-Web interface
configuring with SRC CLI
gateway extension    
description
general properties    
configuring, C-Web interface
configuring, SRC CLI
groups    
configuring with C-Web interface
configuring, SRC CLI
interacting with Web application server    12
loading    
sample data
logging properties    
configuring, C-Web interface    12
configuring, SRC CLI
methods    1
access to    1234
monitoring with SRC CLI
NIC proxies, monitoring    
SRC CLI
NIC proxies, viewing    
C-Web interface
SRC CLI
overview
properties for clients and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
redundancy
sample data    12
scripts    
access to    1234
service sessions    
access to
session handles    
configuring, SRC CLI
SOAP operations, monitoring    
SRC CLI
SOAP operations, viewing    
C-Web interface    12
starting with C-Web interface
starting with SRC CLI
statistics, viewing    
C-Web interface
SRC CLI
subscriber types    
configuring, SRC CLI
test environment    
configuring, SRC CLI    12
PCMM services
testing    1
clients    12
Web application gateway client    12
 

E

events, publishing    123
expanded classifiers    
configuring
 

G

gateway    
SRC    12
gateway extension
 

I

IMS service sessions    
configuring
test environment    
configuring
testing    12
SRC CLI
 

L

local properties    
configuration    
SRC CLI    12
directory location of SRC data, configuring    12
logging properties    
Dynamic Service Activator    1
configuring with C-Web interface    12
 

M

managing    
SAE via external applications    12
services via external application
manuals    
comments on
methods    
Dynamic Service Activator
 

N

namespace, configuration
NIC (network information collector)    
Dynamic Service Activator and
testing    
test data    12
test data, 3GPP Gy
NIC proxies    
cache, configuring    
SRC CLI    12
configuration prerequisites
Dynamic Service Activator    12
NIC replication, configuring    
SRC CLI    123
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI    12
notice icons
 

O

operation    
Dynamic Service Activator
 

P

priorityList    123
publishing events    123
 

R

randomPick    123
redundancy    
Dynamic Service Activator
roundRobin    123
 

S

SAE (service activation engine)    
configuring 3GPP gateway as external plug-in
configuring 3GPP Gy as external plug-in
configuring IMS as external plug-in
managing via external applications    12
scripts    
running on SAE
services    
managing via external application
sessions    
service    
testing
SOAP    
interfaces, public
requests
SRC owners    1
Dynamic Service Activator
SRC SOAP Gateway.     See Web Services Gateway    
static properties
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
 

W

Web application gateway client    
configuring, SRC CLI    12
Web application server    1
interacting with Dynamic Service Activator    12
Web applications    
Web Services Gateway
Web Services Description Language.     See WSDL    
Web Services Gateway    1
clients    1
managing
testing
Web application
wholesaler-retailer environments
WSDL files

SRC 3GPP Gateway Overview

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 Gx interface to mediate between the PCRF and Juniper Networks routers like the E Series Broadband Services routers and MX Series routers. Figure 10 shows an example network configuration where the SRC 3GPP gateway acts as a mediator between the PCRF and an MX Series router. The Gx interface on the SRC 3GPP gateway communicates with the PCRF using the Diameter protocol.

Figure 10: SRC 3GPP Gateway as a Mediator Between the PCRF and an MX Series Router

SRC 3GPP Gateway as a Mediator
Between the PCRF and an MX Series Router

Figure 11 represents the different policy references interfaces you can use, when using the SRC 3GPP gateway with other Juniper Networks products.

Figure 11: Various Interfaces on Juniper Networks Products Communicating with a PCRF Through the SRC 3GPP Gateway

Various Interfaces on
Juniper Networks Products Communicating with a PCRF Through the SRC
3GPP Gateway

The SRC 3GPP gateway supports the following scenarios:

The following sections describe the sequences for each of these scenarios based on using an MX Series router.

Subscriber Login Sequence

The subscriber login uses the following sequence:

  1. A subscriber session logs in and notifies the JSRC within the MX Series router.
  2. The MX Series router sends a Diameter AA-Request (AAR) for the new subscriber session.
  3. The service activation engine (SAE) performs necessary tasks such as creating the user session, provisioning any policy objects, and others.
  4. When the login is complete, the SAE sends back a Diameter AA-Answer (AAA) to the router.
  5. The SAE notifies the SRC 3GPP gateway that a subscriber was logged in successfully. This notification includes information such as the IP Address of the subscriber.
  6. The SRC 3GPP gateway sends a Diameter Credit-Control-Request (CCR) with the following information to the PCRF:
    • CC-Request-Type AVP: INITIAL_REQUEST
    • Framed-IP-Address AVP: user equipment IPv4 address or Framed-IPv6-Prefix AVP: user equipment IPv6 address
    • Subscription-Id AVP: the login-name SAE plug-in attribute (Subscription-Id-Type set to END_USER_E164(0)) and, if available, the interface description SAE plug-in attribute (Subscription-Id-Type set to END_USER_PRIVATE(4))
    • CalledStationId AVP: Set to virtual router name.

    The SRC 3GPP gateway selects the PCRF according to the referenced Diameter peers under the [edit slot 0 gw-3gpp gx diameter-peer] hierarchy.

  7. The SRC 3GPP gateway receives the Credit-Control-Answer (CCA) message from the PCRF.
    • If the PCRF rejected the CCR-I (initial) by providing an error code in the CCA message, the SRC 3GPP gateway logs the subscriber out using the SAE Common Object Request Broker Architecture (CORBA) interface.
    • If the PCRF accepted the CCR-I, the SRC 3GPP gateway iterates over the provided policy and charging control (PCC) rules (if any) from the CCA message and issues service activate calls for those services.
  8. The SRC 3GPP gateway iterates over PPC Rules from the CCA message and issues service activate calls for those services, if applicable.
  9. For each service to be activated, the SAE issues a Diameter Push-Profile-Request (PPR) to the MX Series router.
  10. The MX Series router sends an acknowledgment to the SAE in a Push-Profile-Answer (PPA) message.
  11. The SAE sends an acknowledgement to the SRC 3GPP gateway.

    The SRC 3GPP gateway collects all the failed service activations and sends a CCR-U (update) to the PCRF to indicate the failure. The SRC 3GPP gateway sets the experimental result code in the CCR-U to DIAMETER_PCC_RULE_EVENT(5142) and includes a charging-rule-report for each failed activation including the rule-name and the rule-failure-code.

Subscriber Logout Sequence

The subscriber logout uses the following sequence:

  1. A subscriber session logs out and notifies the JSRC within the MX Series router.
  2. The router sends a Diameter Session-Termination-Request (STR) to the SAE to indicate that the subscriber has logged out.
  3. The SAE notifies the SRC 3GPP gateway that the service session has stopped.

    For each service stop event, the SRC 3GPP gateway issues a CC-Request to the PCRF that includes:

    • CC-Request-Type AVP: UPDATE_REQUEST
    • Usage-Monitoring-Information AVP includes:
      • Final accounting data
  4. The SAE notifies the SRC 3GPP gateway that the subscriber was logged out successfully. The notification includes one of the following addresses:
    • Framed-IP-Address AVP: user equipment IPv4 address
    • Framed-IPv6-Prefix AVP: user equipment IPv6 address
  5. The SRC 3GPP gateway sends a Diameter CCR message with the following information to the PCRF:
    • CC-Request-Type AVP: TERMINATION_REQUEST
    • Subscriber-Id AVP includes one of the following addresses:
      • Framed-IP-Address AVP: user equipment IPv4 address
      • Framed-IPv6-Prefix AVP: user equipment IPv6 address
  6. The SRC 3GPP gateway receives the CCA message from the PCRF.
  7. The SAE acknowledges the STR sent by the router by sending a Session-Termination-Answer (STA) to the router.

Subscriber Session Termination Sequence (Initiated by PCRF)

When the PCRF initiates the subscriber session termination, the following sequence occurs:

  1. The application function requests the termination of the session from the PCRF.
  2. The PCRF issues a Re-Auth-Request (RAR) message, which includes the Session-Release-Cause AVP.
  3. The SRC 3GPP gateway issues a subscriber disconnect CORBA Call to the SAE. This method is not supported for JunosE Point-to-Point Protocol (PPP) sessions; in that case, the SRC 3GPP gateway only logs the subscriber out.
  4. The SAE performs the necessary steps to disconnect the subscriber. For JunosE PPP sessions, the subscriber is logged out using the subscriber logout procedure.
  5. The user equipment is disconnected.
  6. The router sends an acknowledgement to the SAE.
  7. The SAE acknowledges the CORBA Call by sending an acknowledgement to the SRC 3GPP gateway.
  8. The SRC 3GPP gateway acknowledges the RAR message sent by the PCRF by sending a Re-Auth-Answer (RAA) message to the PCRF.
  9. The SAE sends a Subscriber Stop Event message to the SRC 3GPP gateway.
  10. The SRC 3GPP gateway sends a CCR with the following information to the PCRF:
    • CC-Request-Type AVP: TERMINATION_REQUEST
    • Subscriber-Id AVP includes one of the following addresses:
      • Framed-IP-Address AVP: user equipment IPv4 address
      • Framed-IPv6-Prefix AVP: user equipment IPv6 address
  11. The SRC 3GPP gateway receives the CCA message.

Service Activation Sequence (Initiated by Application Function)

When the application function (AF) initiates a service activation, the following sequence occurs:

  1. The AF receives any kind of trigger to set up a new AF session and issues an AAR message to the PCRF.
  2. The PCRF stores all received service information, retrieves profiles, and sends an AA-Answer (AAA) message back to the AF.
  3. The PCRF issues an RAR message, with the Charging-Rule-Install AVP set.
  4. The SRC 3GPP gateway issues a subscriber activate service session CORBA Call to the SAE, by using the Bearer-Identity AVP (subscriber’s IP address) and service name (Charging-Rule-Name AVP).
  5. The SAE performs the necessary steps to activate the specified service for the given subscriber, including sending a Push-Profile-Request (PPR) message to the router.
  6. The router sends an acknowledgement (PPA) to the SAE.
  7. The SAE acknowledges the CORBA Call by sending an acknowledgement to the SRC 3GPP gateway.
  8. The SRC 3GPP gateway sends an Re-Auth-Answer (RAA) message to the PCRF.
  9. The SAE sends Service Start Event to the SRC 3GPP gateway.

Service Modification Sequence (Initiated by Application Function)

When the application function (AF) initiates a service modification, the following sequence occurs:

  1. The AF receives any kind of trigger to update an existing AF session and issues an AAR message to the PCRF.
  2. The PCRF stores all received service information, retrieves profiles, and sends an AA-Answer (AAA) message back to the AF.
  3. The PCRF issues an RAR message, with the Charging-Rule-Install AVP set.
  4. The SRC 3GPP gateway issues a subscriber-modify service CORBA Call to the SAE, which includes the subscriber IP address and the service name (Charging-Rule-Name AVP).
  5. The SAE performs the necessary steps to modify the specified service for the given subscriber, including sending a Push-Profile-Request (PPR) message to the router.
  6. The router sends an acknowledgement (PPA) to the SAE.
  7. The SAE acknowledges the CORBA Call by sending an acknowledgement to the SRC 3GPP gateway.
  8. The SRC 3GPP gateway sends a Re-Auth-Answer (RAA) message to the PCRF.

Service Deactivation Sequence (Initiated by Application Function)

When the application function (AF) initiates a service deactivation, the following sequence occurs:

  1. The AF receives any kind of trigger to terminate or deactivate an existing session and issues an AAR message to the PCRF.
  2. The PCRF stores all received service information, retrieves profiles, and sends an AA-Answer (AAA) message back to the AF.
  3. The PCRF issues an RAR message with the Charging-Rule-Remove AVP set.
  4. The SRC 3GPP gateway issues a subscriber-deactivate service CORBA Call to the SAE.
  5. The SAE performs the necessary steps to deactivate the specified service for the given subscriber, including sending a Push-Profile-Request (PPR) message to the router.
  6. The router sends an acknowledgement Push-Profile-Answer (PPA) to the SAE.
  7. The SAE acknowledges the CORBA Call by sending an acknowledgement to the SRC 3GPP gateway.
  8. The SRC 3GPP gateway sends a Re-Auth-Answer (RAA) message to the PCRF.
  9. The SAE sends a Service Stop Event to the SRC 3GPP gateway. The SRC 3GPP gateway issues a CCR to the PCRF including:
    • CC-Request-Type AVP: UPDATE_REQUEST
    • Usage-Monitoring-Information AVP includes:
      • Final accounting data

Related Documentation

Modified: 2016-05-26