Create a Time Normalizer Template

This normalizer template uses the event start time for a time range normalizer. If an event crosses from one time range to another during rating, the event is measured across the ranges and the rate associated with each time range is used to rate the quantity in that range. The time range normalizer defines multiple ranges that the field value can map to during rating and span across, if necessary.

Procedure

In Normalizer Templates, click New Normalizer Template.
In Create New Normalizer Template:
1. In Name, enter a unique name.
2. In Normalization Algorithm, select Time.
3. Click Create.
In Edit Normalizer Template, in Time Zone Basis, click the time zone to use during rating. The time zone can be associated with the event, event initiator, system, or UTC.
- 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.
(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.
(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.
Click Save to save the new normalizer template.

Attention: Saving the template before entering further data, such as MDC fields, ensures that information you have already entered is not lost.
(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.