Home
Subscriber Management
Subscription-Device Association
When a network message is received, the device information is used to guide the service usage to the subscription. As a result, a subscription can have any number of associated devices.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
MATRIXX Web App Administration
MATRIXX Engine Integration
Call Control Framework Integration
MATRIXX Diameter Integration
MATRIXX 5G Integration
MATRIXX Monitoring and Logging
Pricing and Rating
MATRIXX Pay Now
MATRIXX Policy
MATRIXX Event Streaming
Subscriber Management
- About Subscriber Management
  Subscriber Management provides an overview of subscriber-related data, including users, groups, subscriptions, devices, balances, and notifications. You can capture any attribute of a subscription and base rating on it, enforce subscription and group spending limits across all services and networks, and notify users associated with subscriptions and groups when the subscriptions and groups are nearing spending limits.
- Subscriber Authorization
  MATRIXX Engine supports service authorization and cut-offs to ensure subscriber usage is valid and revenue loss does not occur.
- Subscription-User Association
  You can associate a _glossary/subscription.html with a user in a many-many relationship using the user APIs.
- Subscription-Device Association
  When a network message is received, the device information is used to guide the service usage to the subscription. As a result, a subscription can have any number of associated devices.
  - Device Types
    The MATRIXX Engine supports mobile and login devices. A mobile device uses one or more associated phone numbers to identify the subscription associated with the device. Login devices use a string value (SIP URI (Session Initiation Protocol Uniform Resource Identifier), an NAI (Network Address Identifier), or a PrivateId) for identification.
  - Service Types
    Each network message received for subscriber usage is associated with a service type, and each category of usage within the network message is associated with a service context.
- Managing Subscriptions
  Managing subscriptions includes adding subscriptions to groups, removing subscriptions from groups, setting the status of subscription objects, and associating users with subscriptions. You can perform these operations by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs.
- Managing Devices
  You can create, provision, and delete devices by calling the SubMan APIs and scheduling automated tasks.
- Managing Users
  Managing users includes creating and deleting users, associating users with subscriptions, and assigning users roles. You can perform these operations by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs.
- Managing Product Offers
  Managing product offers includes purchasing and canceling product offers, and removing expired product offers. You can purchase and cancel product offers by using MATRIXX Backoffice Customer Tool and any custom applications that call the SubMan APIs. Expired product offers are removed from subscriber and group wallets automatically after a configured amount of time.
- Rehoming
  Rehoming is the process of moving a user, group, device, or subscription from one sub-domain to a different sub-domain in a multi-domain platform.
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

Subscription-Device Association

When a network message is received, the device information is used to guide the service usage to the subscription. As a result, a subscription can have any number of associated devices.

Unlike most online charging systems that identify a subscriber as a SIM card or device indicator (making them essentially the same entity in the database), MATRIXX treats subscriptions and devices as separate entities. The subscriber object contains pointers to device objects and the device object contains pointers to the subscription registered with the device.

Subscriber and device objects also contain pointers to the product offers that are owned by the subscription and that are valid for the associated device. This makes it possible for a subscription to purchase a data offer and have it apply only to certain devices or to share it across all devices, such as smart phones, residential internet gateways, and tablets—a feature that is not possible with most online charging systems. For example, subscriptions can purchase 100 euros of credit that they can use with their smart phone or a SIM card. Similarly, a subscription can purchase an offer that provides 5 GB of data usage per month that can be used for mobile phone or tablet usage. For more information on how devices are treated with offers, see the discussion about offers with device-specific balances or meters in Pricing and Rating.

A device can have any number of associated phone numbers and can provide access to any number of services, such as voice, data, and messaging. A device can also provide access to any number of service context, such as YouTube®, Netflix®, and iTunes®. When a device accesses a service or service context, the rates to apply are selected based on fields in the incoming network message and rating parameters identified in the pricing. For example, a product offer might have different rates based on the mobile device type and the service context. When rating occurs, the device type is identified, the subscription is looked up, the service context is identified, and the rates that are valid for both parameters are used to update the subscription's balances.

For more information about device types and how to create new devices, see Pricing and Rating.