Create a Phone Number Pattern Match Normalizer Template
The phone number pattern normalizer template defines a phone number field in the network message for comparison with a list of patterns defined in a phone number match normalizer and uses the rating formula associated with the matched pattern.
Procedure
- In Normalizer Templates, click New Normalizer Template.
-
In Create New Normalizer Template:
- In Name, enter a unique name.
- In Normalization Algorithm, select Phone Number Pattern Match.
- Click Create.
- 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.
-
(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:
- Click Add Metadata. This button is disabled if values are defined in the Result Info section.
- Define the following properties:
- Name — The value of the metadata.
- Type — The data type of the metadata.
- Click Create. The metadata defined here appears in the normalizer instance in the Default Metadata table.
- 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
- 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.
-
(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.
-
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.
-
Under Fields, add the fields on which to base normalizations.
For a phone number pattern match, Phone Number Pattern Match Normalization Fields lists the fields that can be the basis of normalizations.
Table 1. Phone Number Pattern Match Normalization Fields Container Name Field Name MtxDiamRoMsg (Accounting - code 271) CalledStationId
MtxDiamRoMsg (Credit Control - code 272) SubscriberIdList.Id
CustomSubscriberObject SpecialCalledStationIdList
For a Diameter Accounting packet (code 271), use the
Calling-Station-Id
AVP for the subscriber's phone number value, which maps to theCalledStationID
field in the MtxDiamRoMsg MDC. For the Credit-Control packet (code 272) and the Tariff packet (code 488), theSubscription-Id
group AVP has two sub-fields:Subscription-Id-Type
andSubscription-Id-Data
. You should use theSubscription-Id-Data
field as the subscriber's identifying phone number.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.- 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.
- 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.
- 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.
- 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.
- Click Create.
-
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.
-
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.
- Click New Called Station Field.
- In New Called Station Field, in Container Name, select the MDC to use for retrieving the B number data from the list.
- In Field Name, select the required MDC field.
- Click Create.