Create a Closed User Group Normalizer Template

This normalizer template defines two MATRIXX Data Container (MDC) fields to check to determine whether the subscriber initiating the event is in the same group as the subscriber receiving the event.

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 Closed User Group.
    3. Click Create.
  3. (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.
  4. (Optional) Under Result Info, select values for the following properties from the drop-down menus.
    Note: The Result values are optional and give a way to copy, to another MATRIXX Data Container (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 decendants:
    • 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 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 the 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.
  5. (Optional) Under Values, enter values for the following properties for each parameter value to add. If you do not set the values in the normalizer template, pricing administrators can set them in the normalizer instance by using My MATRIXX. If you do set the values in the normalizer template, you cannot change them in the normalizer instance.
    Important: For normalizer templates that have only two values, one for a non-match and one for a match, you must define the non-match value first to assign an ID of 0 to it and the match value second to assign an ID 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.
  6. 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.
  7. Under Fields, add the fields on which to base normalizations.
    Add up to two fields, where the first field identifies the callee number, and an optional second field identifies the callee number type.
    1. Click New Field to open the Create Field window.
    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. (Optional) Repeat steps a to c to add a second field specifying the device type of the callee number identified by the first field.
      Note: If not specified, the second field (callee number type) defaults to Imsi. You must specify the callee number type if the first field holds the callee's MSISDN.
      Use one of the following containers, depending on the device type of the callee number:
      • If the device type is Imsi, use MtxMobileDeviceObject.
      • If the device type is AccessNumber (MSISDN), use MtxMobileDeviceAccessObject.
      The following fields are typically specified in the normalizer template.
      Container Name Field Name
      MtxMobileDeviceObject Imsi
      MtxMobileDeviceAccessObject AccessNumber
      MtxLoginDeviceObject LoginId
      MtxLoginDeviceAccessObject AccessId