Home
MATRIXX Architecture
MATRIXX Engine Software Topology
The MATRIXX Real-Time Engine software consists of a set of core software servers and one or more business modules. This is called a MATRIXX server.
System Monitoring and Control
Designed to be highly available, MATRIXX Engine is capable of being monitored and administered remotely. System health and performance are constantly monitored while collecting statistics on a configured interval for blade-level processes and cluster-level processes. These are stored in the statistics database.
MATRIXX SNMP Agent
MATRIXX uses SNMP Agents to monitor the health of its environment. SNMP Agents run on the entire MATRIXX platform and on its major components. For example, it runs on MATRIXX Engine, Traffic Routing Agent (TRA), Network Enabler (NE), Route Cache, and on the MATRIXX web-facing components.
Collecting MATRIXX Diagnostic Statistics
Out-of-the-box, MATRIXX runs the capture_diagstats_tofile.py script every five minutes to collect important SNMP system statistics that you use to assess the condition of its various components.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
- About MATRIXX Architecture
  MATRIXX Architecture provides a high-level overview of MATRIXX core components and functionality. It also provides reference architectures for MATRIXX deployments.
- MATRIXX Introduction
  MATRIXX is a real-time, transactional system designed to more efficiently support the growing volume and complexity of services that require real-time processing.
- MATRIXX Overview
  MATRIXX core components receive network messages, perform event-transaction processing, archive data needed for engine high availability or for disaster recovery, and publish or store event-transaction data for use by other systems.
- MATRIXX Reference Architecture
  A MATRIXX reference configuration runs in Kubernetes clusters in a private or public cloud.
- Multi-Domain Deployments
  Multi-domain MATRIXX deployments allow different pricing plans, MATRIXX Data Container (MDC) definitions, and RS Gateway instances for each domain.
- MATRIXX Engine High Availability and Scalability
  MATRIXX uses features of Kubernetes and Helm to ease high availability (HA) and scalability of components.
- MATRIXX Domain Architecture
  A customer domain is a set of subscribers that co-exist with a single homogeneous pricing configuration. It provides pricing and configuration separation from other potential MATRIXX environments in their own domains, such as in multi-tenancy or testing situations. You can build a customer domain upon one or more sub-domains. The simplest MATRIXX Engine deployment is a single engine chain implementing one customer domain (one customer sub-domain).
- MATRIXX 5G Interface (SBA Gateway)
  MATRIXX SBA Gateway provides a 5G interface for a Charging Server (OCS) and converged charging service (CCS) (including authorization and authentication) and is the consumer for Nchf_ConvergedCharging and Nchf_SpendingLimitControl for spending limit reporting. It is delivered as several images.
- MATRIXX TM Forum Gateway
  MATRIXX TM Forum Gateway (TMF Gateway) is deployed in a cloud native environment and implements the set of TMF microservice APIs supported by MATRIXX.
- MATRIXX Business API Gateway
  MATRIXX Business API Gateway includes the Rest Services (RS) Gateway and Gateway Proxy that translate REST and Java communication into the MATRIXX Data Containers (MDCs) that the other MATRIXX components use to communicate. This gateway is implemented as a high availability (HA) pair for reliability.
- MATRIXX Business API SDK
  The Business API SDK is a framework that includes a set of tools to manage, customize, and extend RS Gateway for your business needs.
- MATRIXX Traffic Routing Agent
  The MATRIXX Traffic Routing Agents (TRAs) load balance and route traffic among the MATRIXX components and provide high availability (HA) protection. Depending on their function, the TRAs can also load balance traffic and serve as a Diameter peer. In addition to HA protection, TRAs also provide a single virtual IP address point of access for BSS systems and network nodes to send network traffic to.
- MATRIXX Route Cache Controller
  In a MATRIXX environment where multiple customer sub-domains are implemented, the Route Cache (a database) is required in the traffic-routing layer.
- MATRIXX SIGTRAN Network Enabler Components
  The MATRIXX SIGTRAN Network Enabler is a MATRIXX service that load balances TCAP messages across the MATRIXX Engine processing servers, which provides charging and balance control operations. In terms of RFC4666 (M3UA), each Network Enabler acts as a signaling gateway process (SGP) and the MATRIXX services on the processing servers act as application server processes (ASPs).
- MATRIXX Applications
  MATRIXX is comprised of several applications that run seamlessly on one MATRIXX Engine to provide a total solution.
- MATRIXX Event Streaming Framework
  Used in environments in which the MATRIXX Event Streaming feature is enabled, or where event loading with MATRIXX Event File (MEF) is used, the Event Streaming Framework is a gateway that connects a MATRIXX Engine cluster to external systems that consume the event streams.
- MATRIXX Engine Software Topology
  The MATRIXX Real-Time Engine software consists of a set of core software servers and one or more business modules. This is called a MATRIXX server.
  - Business Logic Framework
    MATRIXX Charging Application and MATRIXX Policy Application each consist of the MATRIXX Engine event-processing platform and a set of business logic modules. The underlying engine provides the transaction-processing foundation and the modules provide the charging and policy functionality.
  - Algebraic-Decision Technology
    MATRIXX Charging Application can calculate rates and MATRIXX Policy Application can make policy decisions extremely quickly and efficiently because both solutions use linear equations rather than step-by-step hierarchical checks to determine calculations during rating.
  - Transaction Processing
    The processing of each event takes place within an implicit transactional context that is created as the event enters the business logic processing workflow. The transactional context captures the changes to all in-memory database objects that are updated throughout the process flow and the data associated with the processed event.
  - Task Processing
    Internal tasks related to data management operations are performed in the background by the MATRIXX Task Manager so transaction processing is minimally impacted. The Task Manager runs on the processing pods. Each one performs tasks concurrently in MATRIXX Engine so the workload is distributed evenly across the processing pods in an engine.
  - System Monitoring and Control
    Designed to be highly available, MATRIXX Engine is capable of being monitored and administered remotely. System health and performance are constantly monitored while collecting statistics on a configured interval for blade-level processes and cluster-level processes. These are stored in the statistics database.
    - Cluster Management
      The MATRIXX high availability (HA) functionality provides for continuous operation and integrity of a cluster as a whole in case one or more MATRIXX Engine servers in a cluster fails. It also provides HA for active and standby clusters running in a geographically redundant or distributed environment.
    - MATRIXX Process Controller
      The Process Controller runs on each server and is responsible for monitoring the status of the MATRIXX processes in that server. It also handles the start-up and shutdown operations of the server.
    - MATRIXX System Monitor
      The MATRIXX System Monitor is an optional service that you can use to monitor the status of MATRIXX Engine servers (nodes) to protect them from an overload condition. System Monitor is enabled by default.
    - MATRIXX SNMP Agent
      MATRIXX uses SNMP Agents to monitor the health of its environment. SNMP Agents run on the entire MATRIXX platform and on its major components. For example, it runs on MATRIXX Engine, Traffic Routing Agent (TRA), Network Enabler (NE), Route Cache, and on the MATRIXX web-facing components.
      - Monitoring MATRIXX SNMP Statistics
        By default, the SNMP Agent running on a MATRIXX Engine monitors the status and health of all the servers and clusters it has. It collects statistics to aid in identifying potential processing issues.
      - Collecting MATRIXX Diagnostic Statistics
        Out-of-the-box, MATRIXX runs the capture_diagstats_tofile.py script every five minutes to collect important SNMP system statistics that you use to assess the condition of its various components.
      - Monitoring MATRIXX Traffic Routing Agent
        Traffic Routing Agent SNMP statistics are defined in the matrixx_tra_mib.txt MIB file and are returned by the print_snmp_stats.py script when run on any of the Traffic Routing Agent servers. They include categories such as TCP traffic, UDP traffic, Diameter Gateway traffic, and MDC Gateway traffic.
  - Transaction Protocol
    Transaction Protocol is the MATRIXX Engine configuration for processing transactions. This protocol supports up to three processing servers. Two publishing servers are required.
- MATRIXX Engine Data Model
  The MATRIXX Engine data model is object based. All objects are defined in XML, making them extendable and the in-memory databases highly configurable.
- MATRIXX Engine Modules
  The MATRIXX Engine modules run on top of MATRIXX Engine and contain the business logic for MATRIXX Telco applications.
- MATRIXX Security
  MATRIXX should be deployed within a secure area of a carrier's network. Servers should have limited access points for event processing, business support systems, maintenance and monitoring, and local access.
- CAMEL Gateway
  In a MATRIXX environment in which Call Control Framework (CCF) is enabled, you can deploy multiple CAMEL Gateway servers in separate pods outside MATRIXX Engine.
- MATRIXX Traffic Routing Agent DR Features
  MATRIXX Traffic Routing Agent (TRA) provides an isolation layer between the network and the MATRIXX Engines configured as a Disaster Recovery (DR) group. It is installed on a pod located between the network and the MATRIXX Engine DR group and provides a single virtual IP address to which the network sends traffic independent of which engine is active at any given time.
- Transaction Replay
  Transactions are replayed first from all MATRIXX Engine processing pods in an engine to the active publishing pod in that engine. This creates the first redundant set of transaction events.
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
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Collecting MATRIXX Diagnostic Statistics

Out-of-the-box, MATRIXX runs the capture_diagstats_tofile.py script every five minutes to collect important SNMP system statistics that you use to assess the condition of its various components.

MATRIXX Support recommends that you use the output from this script for diagnostic purposes, and send these files to MATRIXX when you report a issue. The capture_diagstats_tofile.py script runs on a configurable interval continuously, storing diagnostic statistics files in $MTX_LOG_DIR, where they are available for inspection. The files are named with this syntax:

snmp_engine_id-stats.log

For example: mtx-1.1.1-127.0.0.1-stats.log

The capture_diagstats_tofile.py script closes, compresses, and adds a timestamp suffix to the filename every 24 hours by default and replaces it with a new log file.

For example: mtx-1.1.1-127.0.0.1-stats.log-2021_02_17_13_47_17.gz

You can change this time interval or specify a file size limit to close, rename, and replace this file; the default is every 24 hours. The interval at which the script runs and the acceptable size and compression level of the output files are configurable.

For more information about how to configure capture_diagstats_tofile.py, see the discussion about capture_diagstats_tofile.py in MATRIXX Monitoring and Logging.