Usage Trigger Properties

Usage Trigger Profile Properties lists the usage trigger profile properties.

Table 1. Usage Trigger Profile Properties
Property Description
ID A unique, positive integer that identifies the virtual field in MATRIXX Engine.
Name A descriptive name for the virtual field, which gets displayed in Virtual Fields in My MATRIXX.
External ID (Optional) A field that you can use to specify the virtual field in MATRIXX pricing objects. External IDs are saved to the pricing configuration file and loaded into the Pricing database. The value of an External ID can be set to any alphanumeric characters that are meaningful to your environment.
Gy Triggers Lists the Diameter Gy triggers that your usage trigger profile can use to change rating for a rating group. These reflect the acceptable values for the Gy Trigger-Type AVP as specified in the 3GPP TS 32.299 specification. They are listed by string in the My MATRIXX user interface, and they are listed here with their Diameter message reference numbers:
  • 1: CHANGE_IN_SGSN_IP_ADDRESS
  • 2: CHANGE_IN_QOS
  • 3: CHANGE_IN_LOCATION
  • 4: CHANGE_IN_RAT
  • 5: CHANGE_IN_UE_TIMEZONE
  • 10: CHANGEINQOS_TRAFFIC_CLASS
  • 11: CHANGEINQOS_RELIABILITY_CLASS
  • 12: CHANGEINQOS_DELAY_CLASS
  • 13: CHANGEINQOS_PEAK_THROUGHPUT
  • 14: CHANGEINQOS_PRECEDENCE_CLASS
  • 15: CHANGEINQOS_MEAN_THROUGHPUT
  • 16: CHANGEINQOS_MAXIMUM_BIT_RATE_FOR_UPLINK
  • 17: CHANGEINQOS_MAXIMUM_BIT_RATE_FOR_DOWNLINK
  • 18: CHANGEINQOS_RESIDUAL_BER
  • 19: CHANGEINQOS_SDU_ERROR_RATIO
  • 20: CHANGEINQOS_TRANSFER_DELAY
  • 21: CHANGEINQOS_TRAFFICE_HANDLING_PRIORITY
  • 22: CHANGEINQOS_GUARANTEED_BIT_RATE_FOR_UPLINK
  • 23: CHANGEINQOS_GUARANTEED_BIT_RATE_FOR_DOWNLINK
  • 24: CHANGEINQOS_APN_AGGREGATE_MAXIMUM_BIT_RATE
  • 30: CHANGEINLOCATION_MCC
  • 31: CHANGEINLOCATION_MNC
  • 32: CHANGEINLOCATION_RAC
  • 33: CHANGEINLOCATION_LAC
  • 34: CHANGEINLOCATION_CELLID
  • 35: CHANGEINLOCATION_TAC
  • 36: CHANGEINLOCATION_ECGI
  • 40: CHANGE_IN_MEDIA_COMPOSITION
  • 50: CHANGE_IN_PARTICIPANTS_NMB
  • 51: CHANGE_IN_THRSHLD_OF_PARTICIPANTS_NMB
  • 60: CHANGE_IN_SERVICE_CONDITION
  • 61: CHANGE_IN_SERVING_NODE
  • 62: CHANGE_IN_ACCESS_FOR_A_SERVICE_DATA_FLOW
  • 70: CHANGE_IN_USER_CSG_INFORMATION
  • 71: CHANGE_IN_HYBRID_SUBSCRIBED_USER_CSG_INFORMATION
  • 72: CHANGE_IN_HYBRID_UNSUBSCRIBED_USER_CSG_INFORMATION
  • 73: CHANGE_OF_UE_PRESENCE_IN_PRESENSE_REPORTING_AREA
  • 74: CHANGE_IN_SERVING_LMN_RATE_CONTROL
  • 75: CHANGE_IN_APN_RATE_CONTROL
  • 76: CHANGE_IN_3GPP_PS_DATA_OFF
5G Trigger Types Lists the 5G triggers that your usage trigger profile can use to change rating either for a specific rating session or for a rating group. These correspond to the subset of the list of trigger type profiles from 3GPP TS 32.225 5G data connectivity domain charging; stage 2. When applicable, the 5G Trigger Value is listed under the trigger type.
  • 8: UNIT_COUNT_INACTIVITY_TIMER
  • 10: QOS_CHANGE
  • 11: VOLUME_LIMIT
    • 5G Trigger Value (in bytes)
    13: EVENT_LIMIT
    • 5G Trigger Value (in event count)
  • 12: TIME_LIMIT
    • 5G Trigger Value (in seconds)
  • 14: PLMN_CHANGE
  • 15: USER_LOCATION_CHANGE
  • 16: RAT_CHANGE
  • 17: UE_TIMEZONE_CHANGE
  • 19: MAX_NUMBER_OF_CHANGES_IN_CHARGING_CONDITIONS
  • 22: CHANGE_OF_3GPP_PS_DATA_OFF_STATUS
  • 23: SERVING_NODE_CHANGE
  • 24: REMOVAL_OF_UPF
  • 25: ADDITION_OF_UPF
  • 26: SESSION_AMBR_CHANGE
  • 28: GFBR_GUARANTEED_STATUS_CHANGE
5G Trigger Categories 5G trigger categories include:
  • IMMEDIATE_REPORT — When the Policy and Charging Enforcement Function (PCEF) encounters a rating change condition, such as when a tariff time change boundary is reached or a subscriber changes cell towers, it sends a 5G Charging Data Request message to MATRIXX Engine with the usedUnitContainer AVP containing the used units and trigger type/condition (tariff time change, validity time (reserved time), quota exhausted). A session field mapping evaluates the trigger type and MATRIXX Engine initiates rating to calculate the cost to the subscriber's balances.
  • DEFERRED_REPORT — The PCEF stores rating change conditions and their unit values and then sends all usedUnitContainer values in the same 5G Charging Data Request message. The event generated for a deferred trigger category only refers to the first evaluated trigger type condition. However, the used units refer to all totalVolume amounts in the multiple usedUnitContainer(s) received in the 5G charging data request message. The Charging Server generates two separate events, one for the Used Service Unit (USU) with the trigger type TTC and one for the USU that follows.
Usage Trigger Component Properties lists the usage trigger components properties.
Table 2. Usage Trigger Component Properties
Property Description
ID A unique, positive integer that identifies the virtual field in MATRIXX Engine.
Name A descriptive name for the virtual field, which gets displayed in Virtual Fields in My MATRIXX.
External ID (Optional) A field that you can use to specify the virtual field in MATRIXX pricing objects. External IDs are saved to the pricing configuration file and loaded into the Pricing database. The value of an External ID can be set to any alphanumeric characters that are meaningful to your environment.
Start Date The day, month, and year that sets when the usage trigger becomes activated in the pricing database.

For revisions, the start date defaults to the date the revision is created. Setting future start dates allows you to have several inactive revisions, with each one becoming valid as soon as the start date occurs. Only one revision can be active in the system at one time.

Usage Trigger Scope Determines how the usage trigger component is applied, either on a session or to a rating_group.
Usage Trigger Tables For information, see the discussion about decision table properties.