Home
MATRIXX Subscriber Management API
Subscriber Management
The following information is an overview of the SubMan APIs and architecture.
Subscriber Data
MATRIXX Engine maintains transactional subscriber data that enables you to address in real time subscriber needs and service usage. The MATRIXX subscriber model is flexible and supports any type of subscriber base, such as retail, wholesale, and Mobile Virtual Network Operator (MVNO).
Subscriber Data Model
MATRIXX Engine maintains transactional subscriber data that enables you to act in real-time to subscriber needs and service usage. The subscriber management data model is exposed through MATRIXX Data Container (MDC) definitions.
Subscription Data Relationships
The MATRIXX Engine in-memory data model is object based. All objects are defined in XML, making the objects easily extendable and the in-memory databases highly configurable. The majority of the objects associated with a subscription are contained in the subscriber database for easy lookup.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
- About Subscriber Management API
  MATRIXX Subscriber Management API provides information about the MATRIXX Engine APIs, including functions, syntax, and result codes, and the MATRIXX Engine REST and Java API implementations.
- Subscriber Management
  The following information is an overview of the SubMan APIs and architecture.
  - SubMan Overview
    The Subscriber Management (SubMan) API defines a set of programming interfaces to the MATRIXX in-memory databases.
  - Architecture and Deployment
    The SubMan API is the externally visible element of the Subscriber Management interface. The interface uses a standard client-server model, where a MATRIXX gateway is the server and any external application that needs to access and manipulate data related to subscribers and groups is the client. The SubMan AP has two language bindings: Java and REST.
  - Message Workflow
    The diagrams in this section show the API message workflow for primary and secondary resources.
  - Data Objects
    An external application or system can use the SubMan APIs to perform operations on primary, secondary, and embedded objects. Primary objects can be called directly by the API and include subscribers, groups, devices, and users. Wallets are secondary objects because they belong to a primary object. Operations on wallets must reference a primary object. Embedded objects include product offers, balances, thresholds, and billing cycles.
  - Subscriber Data
    MATRIXX Engine maintains transactional subscriber data that enables you to address in real time subscriber needs and service usage. The MATRIXX subscriber model is flexible and supports any type of subscriber base, such as retail, wholesale, and Mobile Virtual Network Operator (MVNO).
    - Subscription-Related Database Objects
      Database objects related to subscriptions include: subscriber, device, group, user, wallet, balance, balanceSet, product offer, bundle, session, activity, and event.
    - Subscriber Data Model
      MATRIXX Engine maintains transactional subscriber data that enables you to act in real-time to subscriber needs and service usage. The subscriber management data model is exposed through MATRIXX Data Container (MDC) definitions.
      - Subscription Data Relationships
        The MATRIXX Engine in-memory data model is object based. All objects are defined in XML, making the objects easily extendable and the in-memory databases highly configurable. The majority of the objects associated with a subscription are contained in the subscriber database for easy lookup.
      - Exporting Subscription Data
        MATRIXX provides a Java utility, data_export.jar, which uses checkpoint files to transform the database contents and MATRIXX Event Files (MEFs) to comma-separated value (CSV) files. The data_export.jar file also creates SQL files for creating RDBMS tables and loading the data from the CSV files.
      - Subscriber Database Compression
        Service providers can enable compression for the subscriber database, which aims to compress the memory requirement of each contained object by a ratio of 3:1. This feature can be useful to service providers who have a large subscriber base.
    - MATRIXX Data Containers
      MATRIXX Data Containers (MDCs) are the fundamental data structures used by MATRIXX. They hold objects in the in-memory databases and carry messages through the system. The messages are for incoming network events, subscriber care activities, pricing updates, and any activity that must be handled transactionally.
  - Functions
    The SubMan API functions provide a standardized way to define, send, and receive MATRIXX data. They support generic arguments so applications can use the same programming primitives to communicate with MATRIXX Engine.
  - Syntax
    The generic syntax of each API request and response operation includes a description, the base MDC container used by the operation, and the data elements used by the operation.
  - SubMan API Result Codes
    Each response includes a basic result code indicating success or failure and textual information about any failure. A result code of 0 (zero) is a success and a result code of nonzero is a failure.
  - Domain Routing
    The SubMan API calls include domain routing information.
  - Execute Mode
    The SubMan API execute mode determines if data changes are saved to the internal database when a SubMan API call is made and if credit limits are ignored.
  - MDC Serialization
    The data container package for MATRIXX Java components provides three different formats for serialization: XML, JSON, and OpenAPI JSON. These serialization formats depend on MATRIXX MDC definition files. MDC serialization describes data containers, structs, simple types, arrays and lists, and special fields.
- Object Management
  The following sections introduce how the various in-memory objects are managed.
- SubMan API Reference
  The SubMan API reference includes SubMan API and MDC descriptions.
- REST API Management
  RS Gateway supports the REST API bindings for accessing subscriber data in MATRIXX Engine. RS Gateway consists of an rsgateway application and a set of REST APIs.
- REST API Reference
  This part describes how to use the REST API bindings to interface with MATRIXX Engine.
- Java API
  This part provides an overview of how to use the Java™ API binding for the SubMan v3 API as an interface to the MATRIXX Engine.
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Subscription Data Relationships

The MATRIXX Engine in-memory data model is object based. All objects are defined in XML, making the objects easily extendable and the in-memory databases highly configurable. The majority of the objects associated with a subscription are contained in the subscriber database for easy lookup.

The following relationships exist between subscriber (subscriptions), group, device, and wallet objects:

Subscriber
- A subscription owns exactly one wallet.
- A subscription can own zero or more devices.
- A subscription can be a member of zero or more groups.
- A subscription can own zero or more purchased product offers.
- A subscription can own zero or more purchased bundles.
Group
- A group owns exactly one wallet.
- A group can have zero or more subscriptions as members.
- A group can have zero or more groups as members.
- A group can have exactly one group as a parent.
- A group can own zero or more purchased product offers.
- A group can own zero or more purchased bundles.
Device
- A device can be owned by exactly one subscription.
- A device can own zero or more purchased product offers.
- A device can own zero or more purchased bundles.
User
- A user can own zero or more subscriptions and/or groups.
- A user can be an administrator for zero or more groups.
- A user can be an observer for zero or more subscriptions and/or groups.
Wallet
- A wallet can own exactly one billing cycle.
- A wallet can own zero or more balances.

These relationships are identified in the data diagram with the following connection types:

Figure 1 represents these data relationships graphically. Each arrow represents a pointer to the MATRIXX Data Container (MDC) object being referenced for information and provides information about how many objects can be referenced.

Figure 1. Subscription Data Relationship Diagram