Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Mapping Between SRC Software, Junos OS, and PCC or ePCC Concepts

    This section describes the mapping between the SRC software, Junos OS, and PCC or ePCC concepts. Table 1 lists the mapping between SRC software and Junos OS terminology and the PCC or ePCC function terminology.

    Table 1: SRC Software and Junos OS Terminology Versus PCC or ePCC Terminology

    SRC Software and Junos OS Terminology

    PCC or ePCC Terminology

    Subscriber session

    IP CAN Session

    Service associated with service policies

    PCC Rule

    Service associated with application policies

    ePCC Rule

    Service activation

    Rule-Install

    Service deactivation

    Rule-Remove

    Service accounting

    Usage-Monitoring

    Subscriber Session Termination

    Subscriber Session Detach

    Policies, defined by the SRC software

    Dynamic Rule

    Charging Rule Installation (Service Activation)

    SRC software can activate any number of predefined PCC or ePCC rules in the same CCA-I or RAR message by providing a Charging-Rule-Install AVP. The Charging-Rule-Install AVP is sent for each service session to be activated. The Charging-Rule-Install AVP can contain multiple Charging-Rule-Name AVPs, one for each static PCC rule or contain multiple Charging-Rule-Definition AVPs, one for each dynamic PCC rule or ePCC rule.

    Note: The names appearing in the Charging-Rule-Name AVPs must be unique across all policies for a particular subscriber session.

    The Services Control Gateway expects to receive the following Charing-Rule-Install AVP from the SRC software in CCA and RAR messages:

    Charging-Rule-Install ::= < AVP Header: 1001 >
    				*[ Charging-Rule-Definition ] <grouped>
    				*[ Charging-Rule-Name ] 1005
    				*[ Charging-Rule-Base-Name ] 1004
    Charging-Rule-Definition ::= < AVP Header: 1003 >
    				{ Charging-Rule-Name } 1005
    			 	[ Service-Identifier ] 439
    				[ Rating-Group ] 432
    				*[ Flow-Information ] <grouped>
    				[ TDF-Application-Identifier ] 1088
    				[ TDF-Application-Id-Base ] 1100
    			 	[ Flow-Status ] 511
    			 	[ QoS-Information ] <grouped>
    			 	[ Reporting-Level ] 1011
    			 	[ Online ] 1009
    				[ Precedence ] 1010
    				[ Monitoring-Key ] 1066
    				[ Steering-Information ] <grouped>
    				[ Redirect-Information ] <grouped>
    				[ Mute-Notification ] 2809
    				[ Forwarding-Class-Name ] 1104
    				[ LRF-Profile-Name ] 1102
    				[ HCM-Profile-Name ] 1103
    Flow-Information ::= < AVP Header: 1058 >
    				[ Flow-Description ] 507
    				[ ToS-Traffic-Class ] 1014
    				[ Security-Parameter-Index ] 1056
    				[ Flow-Label ] 1057
    				[ Flow-Direction ] 1080
    
    QoS-Inormation ::= < AVP Header: 1016>
    				[ Max-Requested-Bandwidth-UL ] 516
    				[ Max-Requested-Bandwidth-DL  ] 515
    
    Steering-Information ::= <AVP Header: 1108>
    				[ Service-Chain-Identifier ] 1101
    				[ Steering-Uplink-VRF ] 1109
    				[ Steering-Downlink-VRF ] 1110
    				[ Steering-IP-Address ] 1111
    				[ Keep-Existing-Steering ] 1112
    
    Redirect-Information ::= < AVP Header: 1085 >
    				[ Redirect-Support ] 1086
    				[ Redirect-Address-Type ] 433
    				[ Redirect-Server-Address ] 435
    

    Charging Rule Removal (Service Deactivation)

    The SRC software sends a Charging-Rule-Remove AVP for each PCC or ePCC rule in the same CCA-U or RAR message while deactivating a service.

    The following AVPs are expected by the router from the SRC software in CCA-U and RAR messages:

    Charging-Rule-Remove ::= <AVP Header: 1022>
    				[ Charging-Rule-Name ] 1005
    				[ Charging-Rule-Base-Name ] 1004
    

    Charging Rule Report

    The router can send charging rule reports for any number of services in the same CCR-U request or RAA message. This is achieved by providing a Charging-Rule-Report AVP for each failed rule. The Charging-Rule-Report AVP contains a single Charging-Rule-Name AVP.

    Charging-Rule-Report ::= < AVP Header: 1018 >
    						*[ Charging-Rule-Name ]
    						*[ Charging-Rule-Base-Name ]
    						 [ PCC-Rule-Status ]
    						 [ Rule-Failure-Code ]
    
    

    Modified: 2015-06-19