Usage-Monitoring examples

For the description of the specific AVP, see the 7750 SR Gx AVPs Reference Guide.

IP-CAN session Usage-Monitoring

A category-map with gx-session-level-usage-monitoring must be associated with the subscriber host or session:

configure
    subscriber-mgmt
        category-map cat-map-1 create
            gx-session-level-usage

PCRF in RAR sends the following AVPs (among all the other mandatory ones: session-id, and so on.)

Usage-Monitoring-Information
        Monitoring-Key = ‟any-string”  
        Granted-Service-Unit 
            CC-Input-Octets = 1000000
              CC-Output-Octets = 1000000
        Usage-Monitoring-Level = session_level(0)

Event-Trigger = USAGE_REPORT

The node reports usage when the thresholds are reached some time later in the CCR-U. The usage is monitored internally on the node based on the current sla-profile instance.

Usage-Monitoring-Information
        Monitoring-Key = ‟any-string” 
        Used-Service-Unit   
        CC-Input-Octets = 1000000
                 CC-Output-Octets = 1000000   

The PCRF instructs the node to continue Usage-Monitoring with the new thresholds in the CCA-U:

Usage-Monitoring-Information
        Monitoring-Key = ‟any-string”  
        Granted-Service-Unit 
            CC-Input-Octets = 1000000
            CC-Output-Octets = 1000000
        Usage-Monitoring-Level = session_level(0)


Category Usage-Monitoring

Assume that the following category-map is associated with the subscriber host:

*A:7750>config>subscr-mgmt>cat-map# info 
----------------------------------------------
            activity-threshold 1
            credit-exhaust-threshold 50
            category "queue1" create
                queue 1 ingress-egress 
            exit
            category "queue3-5" create
                queue 3 ingress-egress 
                queue 5 ingress-egress 
            exit
            category "rest-queues" create
                queue 2 egress-only 
                queue 4 egress-only 
                queue 6 egress-only 
                queue 7 egress-only 
                queue 8 egress-only 
            exit

The PCRF sends the following AVPs in the RAR message (among all the other mandatory ones: session-id, and so on.)

Charging-Rule-Install 
        Charging-Rule-Name = Cat-Map:cat1 — cat-map rule install

Usage-Monitoring-Information
        Monitoring-Key = ‟queue-1”  
        Granted-Service-Unit 
            CC-Input-Octets = 1000000
            CC-Output-Octets = 1000000
            Usage-Monitoring-Level = PCC_RULE_LEVEL (1)
Usage-Monitoring-Information
        Monitoring-Key = ‟queue-3-5”  
        Granted-Service-Unit 
            CC-Input-Octets = 2000000
            CC-Output-Octets = 2000000
            Usage-Monitoring-Level = PCC_RULE_LEVEL (1)
Event-Trigger = USAGE_REPORT

The node reports usage when the thresholds are reached some time later in the CCR-U:

Usage-Monitoring-Information
        Monitoring-Key = ‟queue-1” 
        Used-Service-Unit   
               CC-Input-Octets = 1000000
               CC-Output-Octets = 1000000   
Usage-Monitoring-Information
        Monitoring-Key = ‟queue-3-5” 
        Used-Service-Unit   
               CC-Input-Octets = 2000000
               CC-Output-Octets = 2000000   
                

The PCRF instructs the node to continue Usage-Monitoring with the new thresholds in the CCA-U:

Usage-Monitoring-Information
        Monitoring-Key = ‟queue-1”  
        Granted-Service-Unit 
            CC-Input-Octets = 1000000
            CC-Output-Octets = 1000000
            Usage-Monitoring-Level = PCC_RULE_LEVEL (1)
Usage-Monitoring-Information
        Monitoring-Key = ‟queue-3-5”  
        Granted-Service-Unit 
            CC-Input-Octets = 2000000
            CC-Output-Octets = 2000000
            Usage-Monitoring-Level = PCC_RULE_LEVEL (1)