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 Gy Overview

The SRC 3GPP Gy feature is a Diameter-based component in the SRC software, which provides integration with the Online Charging System (OCS) to support fixed-mobile convergence (FMC).

SRC’s 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. Figure 11 shows an SRC 3GPP Gy deployment scenario. The northbound Gy interface on SRC’s Gy communicates with the OCS using the Diameter protocol.

Note: SRC’s Gy supports volume-based quota only.

Figure 11: SRC 3GPP Gy Deployment Scenario

SRC 3GPP
Gy Deployment Scenario

The following sections describe the sequences for each of SRC’s Gy supported scenarios based on an MX Series router:

Subscriber Login Sequence

During subscriber login, the SAE notifies a service authorization event to SRC’s Gy for each service to be activated. This event includes information such as login name, service name, session handle, service identifier, and other SAE plug-in attributes.

SRC’s Gy performs the following actions for service activation received through activate-on-login (AOL) or SRC 3GPP gateway:

  1. Sends a Diameter Credit-Control-Request initial (CCR-I) message with the following information to the OCS:
    • CC-Request-Type AVP: INITIAL_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Service-Identifier AVP: Identifier of the service. This AVP is available in the message only if the identifier is configured for the service.

      Note: Gy functionalities require service identifier information, so you must ensure that the identifier is configured for the service.

    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Requested-Service-Unit AVP: Grouped AVP that contains:
        • CC-Input-Octets AVP: Value is always set to zero
        • CC-Output-Octets AVP: Value is always set to zero
        • CC-Total-Octets AVP: Value is always set to zero
  2. Receives the Credit-Control-Answer initial (CCA-I) message from the OCS.
    • If the OCS rejected the CCR-I message by providing an error code in the CCA-I message, SRC’s Gy requests the SAE not to activate the service for the subscriber.
    • If the OCS accepted the CCR-I message, SRC’s Gy requests the SAE to activate the service for the subscriber and saves the received quota information in the service session properties. SAE interacts with the router to activate the service for the subscriber.

    The CCA-I message contains the following information:

    • CC-Request-Type AVP: INITIAL_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Granted-Service-Unit AVP: Grouped AVP that contains:
        • CC-Total-Octets AVP: The number of octets that can be received and sent by the router
        • CC-Input-Octets AVP: The number of octets that can be received by the router from the subscriber
        • CC-Output-Octets AVP: The number of octets that can be sent from the router to the subscriber
        • Final-Unit-Indication AVP: Indicates that the Granted-Service-Unit AVP has final units for the service
        • Volume-Quota-Threshold AVP: Threshold value in octets

Subscriber Logout Sequence

During subscriber logout, the SAE notifies a service stop event to SRC’s Gy for each active service. The event contains accounting statistics received from the router.

For each service stop event, SRC’s Gy issues a CCR termination (CCR-T) message to the OCS that includes:

  • CC-Request-Type AVP: TERMINATION_REQUEST
  • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
  • Service-Identifier AVP: Identifier of the service. This AVP is available in the message only if the identifier is configured for the service.

    Note: Gy functionalities require service identifier information, so you must ensure that the identifier is configured for the service.

  • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
    • Used-Service-Unit AVP: Grouped AVP that contains:
      • CC-Input-Octets AVP: The number of octets received by the router from the subscriber
      • CC-Output-Octets AVP: The number of octets sent from the router to the subscriber
      • CC-Total-Octets AVP: The number of octets received and sent by the router
      • Terminate-Cause AVP: Reason for terminating the service. The value is set to USER_REQUEST.

Service Activation Sequence

When the Application Function (AF), Dynamic Service Activator (DSA), AOL, scheduler, or Volume Tracking Application (VTA) initiates a service activation, the SAE triggers a service authorization event to SRC’s Gy. The event includes information such as login name, service name, session handle, service identifier, and other SAE plug-in attributes. SRC’s Gy performs the following actions:

  1. Sends a Diameter CCR-I message with the following information to the OCS:
    • CC-Request-Type AVP: INITIAL_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Service-Identifier AVP: Identifier of the service. This AVP is available in the message only if the identifier is configured for the service.

      Note: Gy functionalities require service identifier information, so you must ensure that the identifier is configured for the service.

    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Requested-Service-Unit AVP: Grouped AVP that contains:
        • CC-Input-Octets AVP: Value is always set to zero
        • CC-Output-Octets AVP: Value is always set to zero
        • CC-Total-Octets AVP: Value is always set to zero
  2. Receives the CCA message from the OCS.
    • If the OCS rejected the CCR-I message by providing an error code in the CCA message, SRC’s Gy requests the SAE not to activate the service for the subscriber.
    • If the OCS accepted the CCR-I message, SRC’s Gy requests the SAE to activate the service for the subscriber and saves the received quota information in the service session properties. SAE interacts with the router to activate the service for the subscriber.

    The CCA-I message contains the following information:

    • CC-Request-Type AVP: INITIAL_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Granted-Service-Unit AVP: Grouped AVP that contains:
        • CC-Total-Octets AVP: The number of octets that can be received and sent by the router
        • CC-Input-Octets AVP: The number of octets that can be received by the router from the subscriber
        • CC-Output-Octets AVP: The number of octets that can be sent from the router to the subscriber
        • Final-Unit-Indication AVP: Indicates that the Granted-Service-Unit AVP has final units for the service
        • Volume-Quota-Threshold AVP: Threshold value in octets

Service Deactivation Sequence

When the AF, DSA, AOL, scheduler, or VTA initiates a service deactivation, the SAE triggers a service stop event to SRC’s Gy. The event contains accounting statistics received from the router.

SRC’s Gy issues a CCR-T message to the OCS that includes:

  • CC-Request-Type AVP: TERMINATION_REQUEST
  • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
  • Service-Identifier AVP: Identifier of the service. This AVP is available in the message only if the identifier is configured for the service.

    Note: Gy functionalities require service identifier information, so you must ensure that the identifier is configured for the service.

  • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
    • Used-Service-Unit AVP: Grouped AVP that contains:
      • CC-Input-Octets AVP: The number of octets received by the router from the subscriber
      • CC-Output-Octets AVP: The number of octets sent from the router to the subscriber
      • CC-Total-Octets AVP: The number of octets received and sent by the router
      • Terminate-Cause AVP: Reason for terminating the service. The value is set to USER_REQUEST.

Service Accounting Sequence

After the service is activated by the SAE, the following sequences occur:

  1. The SAE updates SRC’s Gy with the used service units received from the router through accounting messages.
  2. SRC’s Gy tracks the quota or threshold usage with the information received from the OCS.
  3. If the quota or threshold is exhausted, SRC’s Gy sends a CCR update (CCR-U) message to the OCS with the following information to request for a new quota:
    • CC-Request-Type AVP: UPDATE_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Service-Identifier AVP: Identifier of the service. This AVP is available in the message only if the identifier is configured for the service.

      Note: Gy functionalities require service identifier information, so you must ensure that the identifier is configured for the service.

    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Requested-Service-Unit AVP: Grouped AVP that contains:
        • CC-Input-Octets AVP: Value is always set to zero
        • CC-Output-Octets AVP: Value is always set to zero
        • CC-Total-Octets AVP: Value is always set to zero
      • Used-Service-Unit AVP: Grouped AVP that contains:
        • CC-Input-Octets AVP: The number of octets received by the router from the subscriber
        • CC-Output-Octets AVP: The number of octets sent from the router to the subscriber
        • CC-Total-Octets AVP: The number of octets received and sent by the router
        • Reporting-Reason AVP: Reason for usage reporting. The value is set to QUOTA_EXHAUSTED, if the granted quota in the Granted-Service-Unit AVP is exhausted. The value is set to THRESHOLD, if the granted quota in Volume-Quota-Threshold AVP is exhausted.
  4. The OCS sends the CCA update (CCA-U) message to SRC’s Gy with the following information:
    • CC-Request-Type AVP: UPDATE_REQUEST
    • Subscription-ID AVP: Login name received from the router as an SAE plug-in attribute
    • Multiple-Service-Credit-Control AVP: Grouped AVP that contains:
      • Granted-Service-Unit AVP: Grouped AVP that contains:
        • CC-Total-Octets AVP: The number of octets that can be received and sent by the router
        • CC-Input-Octets AVP: The number of octets that can be received by the router from the subscriber
        • CC-Output-Octets AVP: The number of octets that can be sent from the router to the subscriber
        • Final-Unit-Indication AVP: Indicates that the Granted-Service-Unit AVP has final units for the service
        • Volume-Quota-Threshold AVP: Threshold value in octets
  5. SRC’s Gy stores the quota in the service session properties.
  6. The SAE updates SRC’s Gy with the used service units received from the router through accounting messages.
  7. SRC’s Gy checks whether the Final-Unit-Indication AVP is stored in the service session properties. If the Final-Unit-Indication AVP is available, SRC’s Gy requests SAE to deactivate the service. For more information about the communication between SRC’s Gy and OCS during service deactivation, see Service Deactivation Sequence.
  8. If the Final-Unit-Indication AVP is not available, SRC’s Gy iterates sending of CCR-U messages to the OCS to request for a new quota.

Related Documentation

Modified: 2015-06-19