Usage Monitoring
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

Usage Monitoring

Usage monitoring is only available when your system is licensed for the feature and you selects LTE Spec Version as 9.4 or higher and AGW I/F is Gx on the Emulator Configuration tab. Usage Monitoring Control data is a collection of monitoring instances.  Each monitoring instance allows you to pre-configure resource monitoring, reporting at the PCEF. PCRF Usage Monitoring requires you to configure these two steps:

All of the parameter associated with defining Monitoring instances and mapping Charging Rules are listed below.

Assignments

 

Monitor

See also:

Usage Monitoring Control

 

Enable Usage Monitoring Control

Select to configure PCRF Usage Monitoring controls :

  • Map Usage-Monitoring instances to an IPCAN or Charge Rules
  • Configure Usage Monitoring Instances

Tcl Parameter: GxSrvUsageMonitorEn
Periodic Query

Use Periodic Query to request for Usage-Monitoring result. You can configure to periodically query the PCEF for accumulated result of either all or individual active monitoring instances of an IP-CAN session of a subscriber.  

Select Periodic Query to indicate whether a configured monitor would be a candidate for periodic query of accumulated usage result.

  • Interval (Sec): Is available when you select Periodic Query and Individual Monitoring Instance is the Query Type default. Enter the time in seconds from last query or activation, for PCRF to send a query.
  • Query Type: Indicates whether you wish to query Individual Monitor Instances or All Monitor Instances.

Tcl Parameter: GxSrvPerQueryEn

Tcl Parameter: GxSrvPerQueryInternal

Tcl Parameter: GxSrvPerQueryType
Time in NTP Format

Available if Initial Usage Threshold Time is selected.  Select to include time in NTP format in CC-TIME AVP (per RFC 4006).

Tcl Parameter: GxSrvUsageMonNtpTimeEn
Number of Monitoring Instances

You may pre-configure a maximum of 10 usage monitoring instances. Select the required Number Of Monitoring Instances.  One instance is selected by default.  

NOTE: The maximum number of 10 monitoring instances supports monitoring of 10 different IPCAN/APNs (maximum of 10 APNs).

Tcl Parameter: GxSrvNumUsageMonitors

 

^ Back to Top

Assignments

The Assignments pane allows you to configure usage monitoring levels and map monitor instances to its IPCAN or charging rules.

Monitoring Level and Session Level Assignments

Use the Monitoring Level and Session Level Assignments to assign individual monitoring instance to IPCAN (APN) or PCC Rule.

The number of rows depend on the Number of Monitoring Instance you selected.

Monitor

 Indicates Monitor 1 to the value selected in the Number of Monitoring Instance.

Monitoring Level

Indicates whether the Monitor instance is provisioned for an IPCAN (APN) session or PCC-Rule(s). Select one the following options. Default is PCC-Rule-Level.

  • PCC-RULE-LEVEL
  • SESSION-LEVEL
NOTES:
  • PCC-RULE-LEVEL: For Usage-Monitoring instances set to the PCC_RULE-LEVEL, use the Rule Level Assignments table to map the charging rules.
  • SESSION-LEVEL: For Usage-Monitoring instances set to SESSION-LEVEL (IPCAN mapping), one monitoring instance can be mapped to only 1 IPCAN session/APN.

 

Assignment
  • For PCC-RULE-LEVEL: Indicates the Rule Set Assigned in the Rule Level Assignments table.
  • For SESSION-LEVEL: Select the required APN you wish to monitor from the dropdown list. The number of APN listed depends on the Number of APNs selected.
NOTE: For an APN you wish to monitor, make sure the following tasks are performed on the PCC Rules tab:

 

 

^ Back to Top

 

Rule Level Assignments  

Use the Rule Level Assignments to assign individual monitoring instance to a Charging Rule.

The number of rows in the Rule Level Assignments table depend on the Number of Rule Set and Charging Rule you defined on the PCC Rules tab. In addition, you may assign separate Rule Sets for IPv4, IPv6, and Dual Stacks, depending on your selection on the PCC Rule Tab.

NOTES: Before you can map a Usage-Monitoring instance to a Charging Rule, make sure that at least one Rule Set and Charging Rule is configured.
  • Enable at least one Rule set
  • Enable at least one Charging Rule within a Rule Set.

Rule Set

The Rule Set depends on the Number of Rule Set and Charging Rule you selected and defined on the PCC Rules tab. For exampleFor example, if you selected 3 Rule Sets and 2 Charging Rule, then 4 Rule set (rows) are displays for assignment.

Charging Rule

The Rule Set depends on the Number of Rule Set and Charging Rule you selected and defined on the PCC Rules tab. See the illustrated exampleexample.

Monitor Assignment

For a charge rule you wish to monitor, go to the Charging Rule row and choose an appropriate monitoring instance from the dropdown.
NOTES: For Usage-Monitoring instances to Charge-Rule mapping:

 

^ Back to Top

Monitor n

The Number of Monitor instance tab depends on value you select in the Number Of Monitoring Instances and is labeled starting Monitor 1 to Monitor n.

NOTE: You may pre-configure a maximum of 10 usage monitoring instances. The maximum number of 10 monitoring instances supports monitoring of 10 different IPCAN/APNs (maximum of 10 APNs).

 

Activation Delay

An Activation Delay of a monitoring instance is a time (in seconds) to delay the start of monitoring after a resource had been granted or established. By default, an activation delay is set to zero.

Tcl Parameter: GxSrvUsageMonActDelay_1

The PCRF signals PCEF to start monitoring right after an IPCAN is established or charge-rule is installed.   

  • When activation delay of a monitoring instance is set to zero, PCRF request PCEF to activate usage monitoring on a successful establishment of IPCAN/APN or successful installation of a new PCC Rule.
  • When activation delay of a monitoring instance is set to a value greater than zero, PCRF delays the activation of usage monitoring till the delay time expires. The PCRF start count down to the delay time right after an IPCAN/APN is established or a PCC rule is installed.
NOTE: The PCRF may delay the installation of a new rule when a ruleset-delay is greater than zero.
Monitoring Key

The Monitoring Key identifies a monitoring instance. The configured value is sent back and forth between PCRF and PCEF for provisioning or reporting usages.  

Range: 64 characters ( mandatory and unique)

Default: Monitor_Key_1

Tcl Parameter: GxSrvUsageMonKey_1

Periodic Query Allowed

Select to indicate that periodic query is enabled and is available only when you select Periodic Query.

Tcl Parameter: GxSrvUsageMonPerQueryEn_1

 

Initial Usage Threshold

An initial usage threshold is a volume of usage threshold in bytes sent from PCRF to PCEF at the activation of Usage Monitoring.  When activated, PCEF accumulates usages of requested monitoring resource and reports to PCRF when accumulated usages reach the threshold specified.

NOTE: You may monitor initial usage threshold of Total Volume, Individual Volume, or Time.

Select to indicate the required initial usage threshold for each monitor instance.

Total Volume (Bytes)

Specify the usage threshold of total volume (all usages).

GxSrvUsageMonInitVolType_1

GxSrvUsageMonInitTotVol_1

Individual Volume

Specify the usage threshold of individual volume for each up/down link direction.

  • Uplink Volume (Bytes)
  • Downlink Volume (Bytes)

GxSrvUsageMonInitVolUplinkEn_1

GxSrvUsageMonInitVolUplink_1

GxSrvUsageMonInitVolDwnlinkEn_1

GxSrvUsageMonInitVolDwnlink_1

Time (s)

Select to indicate the time at which the PCEF reapplies the threshold value provided by the PCRF (Monitoring-Time AVP (AVP Code 2810)).

Select to use time threshold instead of volume threshold and enter a value. The value indicated the time at which the PCEF reapplies the threshold value provided by the PCRF (Monitoring-Time AVP (AVP Code 2810)).

NOTE: The Time threshold specified by a CC-time AVP in the Granted-Server-Usage AVP replaces the volume threshold AVPs in the GSU AVP with the Time value you enter.

Option: 0 - 65535

Default: 60

Tcl Parameter:

GxSrvUsageMonInitVolType_1

GxSrvUsageMonInitTime_1

 

 

^ Back to Top

Modifier

Use the Modifier pane to modify either usage threshold or monitoring key of an active monitor instance.

NOTE: The configured values in the Modifier pane is also used for Auto-Restart Monitoring purposes.

 

Enable Modifier Select to enable the Modifier pane.
Modify Usage Threshold Available only when you select Total or Individual Volume threshold set in the Initial Usage Threshold pane. Select to modify initial volume threshold set. You can select whether to increase or decrease Total Volume or Individual Volume.

GxSrvUsageMonModTotType_1

GxSrvUsageMonModTotVol_1

GxSrvUsageMonModUpType_1

GxSrvUsageMonModUpVol_1

GxSrvUsageMonModDwnType_1

GxSrvUsageMonDwnVol_1
Modify Time Threshold Available only when you select Time  in the Initial Usage Threshold pane. Select to modify initial Time set. You can select whether to increase or decrease Time by a specified value.

GxSrvUsageMonModType_1

GxSrvUsageMonModTimeType_1

GxSrvUsageMonModTime_1

 
 
Modify Monitoring Key

Select Monitoring Key and enter the number of Monitor instance from which the monitoring key will be taken.  

NOTE: Entering a value to Modify Monitoring Key is the same as replacing an active Monitor instance with a new Monitor instance. PCRF replaces current usage threshold of an active monitor with the initial usage threshold of a new instance.

GxSrvUsageMonModType_1

GxSrvUsageMonModInstance_1
Enable Periodic Modify

Select to have PCRF send modify-request to PCEF periodically, that is, for every period set in the Periodic Modify Interval (sec) (value larger than zero).

NOTE: When you select Enable Periodic Modify, the PCRF automatically stops sending request when a service (IPCAN or PCC rule) is terminated.

NOTE: If the Modifier type you have selected becomes disabled by a change in the selected Threshold type, the modifier defaults to Modify Monitoring Key.

 

^ Back to Top

Auto-Start Monitoring

The PCEF stops monitoring for a particular monitor instance after it sends a usage report to the PCRF.  In response to the report, the PCRF decides whether PCEF should continue monitoring for the reported instance or stop monitoring.

Enable Auto-Restart Monitoring

Select to indicate whether to stop or restarting the monitor.

  • When you do not select Enable Auto-Restart Monitoring, the PCRF responds to a report with a not continue monitoring and PCRF does not reinstate a new usage threshold and/or monitoring key.  
  • When you select Enable Auto-Restart Monitoring, the PCRF responds to a report with a continue monitoring and reuse the same monitoring key with a new threshold depending on the following selection:
  • Re-use an initial usage threshold: Select for the PCRF to use a pre-configured initial threshold for continue monitoring.
  • Use Next Value in the Modifier: is available only when you select Enable Modifier. Select for the PCRF to use a next calculated modified threshold, or a new monitoring key if the modifier is configured to use it.
NOTE: When a report was generated due to a service termination (for example due to session terminated, bearer disconnected, rule deactivated, and so on), the PCRF automatically ignores your selection of Auto-Start Monitoring and does not restart the monitoring (behaves as if the Auto Restart Monitoring was not selected).

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.