Pricing Configuration Notification Components

Table 1. Pricing Configuration Notification Components
Pricing Components	Description
Notification Profiles	Notification profiles are reusable pricing components that define when expiration and recurring processing failure notifications are sent and the frequency with which those notifications are sent. Notification profiles can be assigned to each status in offer and status life cycles. You can assign a notification profile ID or a notification profile selector ID, not both. You must create the notification profile or notification profile selector before you can add it to a life cycle status. For more information about creating notification profiles, see the discussion about creating a notification profile in My MATRIXX Help. For more information about status life cycles, see the discussions about status life cycle definitions and status life cycle notifications in MATRIXX Subscriber Management API.
Notification Profiles for Expiration	In My MATRIXX, notification profiles can be assigned to balance, product offer, and bundle definitions for expiration notifications. Each notification profile can be configured to send a notification on expiration and multiple notifications (minutes, hours, days, weeks, months, or years) before and after expiration.
Notification Profiles for Recurring Processing Failure	In My MATRIXX, notification profiles can be assigned to balance templates and billing cycle templates. Each notification profile for recurring processing failure can be configured to send a notification on failure and multiple notifications (minutes, hours, days, weeks, months, or years) after the time of the initial recurring processing failure for the period in which the failure occurred. Note: If recurring processing succeeds (for example, due to a product offer purchase) after a failure and before the time to generate the notification, then the notification is not generated.
Notification Profile Selectors	In My MATRIXX, notification profile selectors use decision tables to determine which notification profiles are selected based on a defined set of criteria. Notification profiles can be assigned to each status in offer and status life cycles. You can assign a notification profile ID or a notification profile selector ID, not both. You must create the notification profile or notification profile selector before you can add it to a life cycle status. For more information about creating notification profiles, see the discussion about creating a notification profile in My MATRIXX Help. For more information about status life cycles, see the discussions about status life cycle definitions and status life cycle notifications in MATRIXX Subscriber Management API.
Balance Templates	Balance templates define if notifications are created when a balance instance in a subscription or group wallet is created and assign notification profiles. Define default credit limit and balance threshold notifications. For balance threshold notifications, the notification preference can be configured to use the group notification preference, or notify group administrators or individual subscribers. Pricing administrators can lock the credit limit and threshold configurations so they cannot be changed after the balance instance is in a subscription or group wallet. Note: In the SubMan APIs, a `NotificationState=true` indicates that notifications on the specified threshold are enabled. Define if notifications are created when a balance expires. For more information about balance notifications, see the discussion about balance notifications in MATRIXX Pricing and Rating.
Product Offers	Product offers define if notifications are created when a catalog item is purchased or canceled for a subscription, group, or device and assign notification profiles. Note: When a purchased offer includes recurring pricing components the charges and grants from the purchase event and the product offer recurring events are included in a single notification (MtxOfferPurchaseNotification). Define if notifications are created when a product offer expires.
Bundles	Bundles define if notifications are created when a bundle is purchased or canceled for a subscription, group, or device, and assign notification profiles.
Recurring Processing Failure Notifications	Configure balance templates, billing profile templates, and product offer cycle data in My MATRIXX to reference a notification profile which defines when notifications are sent after recurring processing fails (the failure to apply recurring charges).
Service Context Termination Notifications	A notification is generated when a session's service context is terminated and context end notification delivery is enabled for that specific context. A session's service context can be terminated in multiple ways, including when a session is terminated with a message of CC-Request-Type `TERMINATE_REQUEST`, a session expires, a session is terminated due to an error, or a context is reset with reporting reason FINAL. If notifications are enabled for termination of a service context, the `ContextEndNotification` is true in SubMan API service context queries.
Final Unit Indication (FUI) Notifications	Define if notifications are created when a FUI profile is selected during rating. For example, notifications can be generated when a phone call cannot be established or continued due to an insufficient prepaid balance amount. To implement this functionality, use a balance distribution normalizer to determine if the `Granted-service-Unit` (GSU) present in the Diameter CCR-I and CCR-U message is zero, and a FUI profile containing a notification request for the operation. If the GSU is zero, the FUI profile is selected, causing a notification to be sent. If a partial amount is authorized, no notification is sent. Pricing administrators can configure FUI notifications in FUI profiles in My MATRIXX.

Notification Profiles

Notification profiles are reusable pricing components that define when expiration and recurring processing failure notifications are sent and the frequency with which those notifications are sent. Notification profiles can be assigned to each status in offer and status life cycles. You can assign a notification profile ID or a notification profile selector ID, not both. You must create the notification profile or notification profile selector before you can add it to a life cycle status.

For more information about creating notification profiles, see the discussion about creating a notification profile in My MATRIXX Help. For more information about status life cycles, see the discussions about status life cycle definitions and status life cycle notifications in MATRIXX Subscriber Management API.

Notification Profiles for Expiration

In My MATRIXX, notification profiles can be assigned to balance, product offer, and bundle definitions for expiration notifications.

Each notification profile can be configured to send a notification on expiration and multiple notifications (minutes, hours, days, weeks, months, or years) before and after expiration.

Notification Profiles for Recurring Processing Failure

In My MATRIXX, notification profiles can be assigned to balance templates and billing cycle templates. Each notification profile for recurring processing failure can be configured to send a notification on failure and multiple notifications (minutes, hours, days, weeks, months, or years) after the time of the initial recurring processing failure for the period in which the failure occurred.

Note: If recurring processing succeeds (for example, due to a product offer purchase) after a failure and before the time to generate the notification, then the notification is not generated.

Notification Profile Selectors

In My MATRIXX, notification profile selectors use decision tables to determine which notification profiles are selected based on a defined set of criteria. Notification profiles can be assigned to each status in offer and status life cycles. You can assign a notification profile ID or a notification profile selector ID, not both. You must create the notification profile or notification profile selector before you can add it to a life cycle status.

For more information about creating notification profiles, see the discussion about creating a notification profile in My MATRIXX Help. For more information about status life cycles, see the discussions about status life cycle definitions and status life cycle notifications in MATRIXX Subscriber Management API.

Balance Templates

Balance templates define if notifications are created when a balance instance in a subscription or group wallet is created and assign notification profiles.

Define default credit limit and balance threshold notifications. For balance threshold notifications, the notification preference can be configured to use the group notification preference, or notify group administrators or individual subscribers.

Pricing administrators can lock the credit limit and threshold configurations so they cannot be changed after the balance instance is in a subscription or group wallet.

Note: In the SubMan APIs, a NotificationState=true indicates that notifications on the specified threshold are enabled.

Define if notifications are created when a balance expires.

For more information about balance notifications, see the discussion about balance notifications in MATRIXX Pricing and Rating.

Product Offers

Product offers define if notifications are created when a catalog item is purchased or canceled for a subscription, group, or device and assign notification profiles.

Note: When a purchased offer includes recurring pricing components the charges and grants from the purchase event and the product offer recurring events are included in a single notification (MtxOfferPurchaseNotification).

Define if notifications are created when a product offer expires.

Bundles

Bundles define if notifications are created when a bundle is purchased or canceled for a subscription, group, or device, and assign notification profiles.

Recurring Processing Failure Notifications

Configure balance templates, billing profile templates, and product offer cycle data in My MATRIXX to reference a notification profile which defines when notifications are sent after recurring processing fails (the failure to apply recurring charges).

Service Context Termination Notifications

A notification is generated when a session's service context is terminated and context end notification delivery is enabled for that specific context. A session's service context can be terminated in multiple ways, including when a session is terminated with a message of CC-Request-Type TERMINATE_REQUEST, a session expires, a session is terminated due to an error, or a context is reset with reporting reason FINAL.

If notifications are enabled for termination of a service context, the ContextEndNotification is true in SubMan API service context queries.

Final Unit Indication (FUI) Notifications

Define if notifications are created when a FUI profile is selected during rating. For example, notifications can be generated when a phone call cannot be established or continued due to an insufficient prepaid balance amount. To implement this functionality, use a balance distribution normalizer to determine if the Granted-service-Unit (GSU) present in the Diameter CCR-I and CCR-U message is zero, and a FUI profile containing a notification request for the operation. If the GSU is zero, the FUI profile is selected, causing a notification to be sent. If a partial amount is authorized, no notification is sent. Pricing administrators can configure FUI notifications in FUI profiles in My MATRIXX.