Create a Date Set Match Normalizer Template

This normalizer template defines a list or an array field in an MATRIXX Data Container (MDC) containing a list of dates or datetimes to compare with the time of an operation, such as the event time in a Diameter message. Normalizers using this template evaluate to a match if the operation is on a date included in the list in the specified MDC field.

Before you begin

Create a custom MDC that includes a field to contain the dates on which to base normalizations. The field can contain one or more dates or datetimes. Only the month and day of each date or datetime in the MDC field is used for comparison in the normalizer, the year, time, and time zone or UTC offset are ignored.

For information about extending MDCs, see MATRIXX Configuration.

Procedure

  1. In Normalizer Templates, click New Normalizer Template.
  2. In Create New Normalizer Template:
    1. In Name, enter a unique name.
    2. In Normalization Algorithm, select Date Set Match.
    3. Click Create.
  3. In Edit Normalizer Template, to base normalizations on fields retrieved from data for the called party (the B number) instead of the caller (the A number), select Use Called Station Field.
    Note: Rating uses the field values and eligibility features from the caller for normalizations by default. For more information about using the B number for normalizations, see the discussion about normalizing on B number.
  4. In Time Zone Basis, select the time zone to use when evaluating the date from the following list:
    • event — Uses the time zone indicated by the incoming network message, which is impacted by the 3GPP-MS-Timezone and Event-Timestamp AVPs. This is the time zone where the event is initiated and is dependent on the initiator's current location, which can vary. It is the default.
    • initiator — Uses the time zone stored with the subscriber's profile information. This time zone is static and is typically the time zone of the subscriber's residence. It is not necessarily the same time zone in which an event is initiated.
    • system — Uses the time zone configured for the MATRIXX Engine. This time zone is also static. It is not necessarily the same time zone in which the system is physically located or indicated by the network message for the event.
    • utc — Based on the time of day of the event, interpreted in the UTC offset contained in the event message.
  5. (Optional) Define metadata values that can be associated with a normalizer results row.
    Important: A normalizer template can either have metadata fields (defined in this step) or fields to use in normalizer chaining (defined in the Result Info section). It cannot have both. Using metadata is the recommended approach.
    Under Metadata:
    1. Click Add Metadata. This button is disabled if values are defined in the Result Info section.
    2. Define the following properties:
      • Name — The value of the metadata.
      • Type — The data type of the metadata.
    3. Click Create. The metadata defined here appears in the normalizer instance in the Default Metadata table.
    4. Click Save to save the normalizer template. After the template is saved, the metadata displays as a column in the Values table.
  6. (Optional) Under Result Info, select values for the following properties from the drop-down menus. These fields are disabled if metadata values are defined.
    Note: The Result values are optional and provide a way to copy, to another MDC field, the description and name values associated with the normalized value chosen during rating. This enables you to add the name and description to the MEF file generated during rating, and to perform further normalizations based on these Result Name Field values (normalizer chaining). For normalizer chaining, use any fields from any of the following containers and their descendants:
    • MtxChargingSessionExtension
    • MtxChrgMsgWorkspace
    • MtxMsg
    • MtxMultiServiceData
    • MtxPolicySessionExtension
    For more information, see the discussion about normalizer chaining in MATRIXX Pricing and Rating.
    • Result Description Container — The target MDC to copy the description of the normalized value chosen during rating to. For example, the MDC name to identify the Diameter message is MtxDiamRoMsg. Select the required MDC from the list.
    • Result Description Field — The target field within the target MDC container to copy the description of the normalized value chosen during rating to. The copy operation occurs only if the field value in the message is not set when normalizer is evaluated. Use dot notation to identify fields nested in the MDC structure. For example, to identify the SMS node role for a session within the Diameter message, you might enter ServiceInfo.SmsInfo.SmsNode.
    • Result Name Container — The target MDC to copy the name of the normalized value chosen during rating to. Select the required MDC from the list.
    • Result Name Field — The target MDC field within the target MDC container to copy the name of the normalized value chosen during rating to. Use dot notation to identify nested fields.
  7. Under Values, enter values for the following properties for each parameter value to add.
    Important: This normalizer template has only two values, one for a non-match and one for a match. You must define the non-match value in the first row of the Values table, to assign an ID of 0 to it, and the match value in the second row, to assign an ID value of 1.
    • Name — The name of the parameter value. For example, No Match or Match.
    • Description — A description for the value. The description is visible when mousing over a value in My MATRIXX.
    • Color — Helps to offset each value in a normalizer instance. To assign a color to the parameter, do one of the following:
      • Hover over the Color cell in the row and select a color from the color palette.
      • Click the Color cell in the row and assign a color to the value by setting the color's hue, saturation, and lightness.
    • If metadata is configured for this template, define the metadata values. Either enter a value or one of the following:
      • Enter --none-- if no value is assigned to this field.
      • Enter --default-- to use the default value for this field. Default values are defined in the normalizer instance in the Default Values table.
      These values are applied to all instances of the metadata in the normalizer's Rows table. If no value is defined here, you can define a value in the normalizer instance.
  8. Click Save to save the new normalizer template. If a name is not provided for both required values, Save is disabled.
    Attention: Saving the template before entering further data, such as MDC fields, ensures that information you have already entered is not lost.
  9. Under Fields, add the field containing the list of dates or datetimes on which to base normalizations.
    Important: A normalizer template can either have parameters (defined in the Parameters section) or fields (defined in this step). It cannot have both. Both sections are enabled if neither has anything configured. After a field is added, the Parameters section is disabled.
    1. Click Add Field. This button is disabled if values are defined in the Parameters section or the maximum number of fields allowed has already been added. The maximum number of fields allowed is determined by the normalizer algorithm.
    2. In Container Name, select the MDC that holds the field from the drop-down menu. To search for an MDC in the list, begin entering the MDC name.
    3. In Field Name, select the MDC field from the drop-down menu. To search for a field in the list, begin entering the field name.
    4. If the field is in the MtxGroupObject MDC, in Tier, select the group tier name to normalize on. If you do not specify a tier, the group type defaults to global.
    5. Click Create.
  10. Under Parameters, add the catalog item parameters on which to base normalizations. For more information, see the discussion about adding parameters to a catalog item.
    Important: A normalizer template can either have parameters (defined in this step) or fields (defined in the previous step). It cannot have both. Both sections are enabled if neither has anything configured. After a parameter is added, the Fields section is disabled.
    1. Click Add Parameter. This button is disabled if values are defined in the Fields section or the maximum number of parameters allowed has already been added. The maximum number of parameters allowed is determined by the normalizer algorithm.
    2. In Add Parameter, select the parameter to add from the list.
      Tip: You can filter the list of parameters by using the Search field.
    3. Click Add.
  11. If you selected Use Called Station Field, under Called Station Search Data, perform the following steps to specify the MDC and MDC field that normalizers using this template will use for retrieving the B number data.
    1. Click New Called Station Field.
    2. In New Called Station Field, in Container Name, select the MDC to use for retrieving the B number data from the list.
    3. In Field Name, select the required MDC field.
    4. Click Create.