Home
Architecture Overview
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 (blade).

Welcome
Release Notes
Architecture Overview
- About the Architecture Overview
  Architecture Overview provides information about the MATRIXX Digital Commerce™ functionality.
- MATRIXX Digital Commerce Introduction
  MATRIXX Digital Commerce is a real-time, transactional system designed to more efficiently support the growing volume and complexity of services that require real-time processing.
- MATRIXX Digital Commerce Overview
  MATRIXX Digital Commerce core components receive network messages, perform event-transaction processing, archive data needed for engine high-availability or disaster-recovery purposes, and publish or store event-transaction data for use by other systems.
- Virtualization and Cloud Deployment
  MATRIXX Digital Commerce is designed for deployment in public, private, or hybrid clouds as an alternative to on-premise (bare metal) hardware deployment.
- MATRIXX Engine Architecture
  A MATRIXX Engine environment can include an active, a standby, and (optionally) a second standby engine. A MATRIXX Engine must have at least one backup engine, referred to as the standby engine or high-availability (HA) peer. A MATRIXX Engine and its configured standby peers together form an engine chain, which work together for disaster-recovery purposes. Should one engine fail, one of the standby(s) take over. For information about what happens when an active engine fails, see the discussion about disaster recovery.
- MATRIXX 5G Interface (SBA Gateway)
  MATRIXX Digital Commerce 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 a Docker image or RPM file.
- MATRIXX Business API Gateway
  MATRIXX Digital Commerce Business API Gateway includes the RS (REST Services) Gateway and Gateway Proxy that translate REST and Java communication into the MDCs that the other MATRIXX components use to communicate. This gateway is implemented as a high-availability (HA) pair for reliability.
- MATRIXX Traffic Routing Agent
  The MATRIXX Digital Commerce Traffic Routing Agents (TRAs) load-balance and route traffic among the MATRIXX Digital Commerce 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 Digital Commerce SIGTRAN Network Enabler is a MATRIXX service that load balances TCAP messages across the MATRIXX Engine processing blades, 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 blades act as application server processes (ASPs).
- MATRIXX Digital Commerce Applications
  MATRIXX Digital Commerce is comprised of several applications that run seamlessly on one MATRIXX Engine to provide a total solution.
- 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 Event Streaming Framework
  Used in environments in which the MATRIXX Event Streaming feature is enabled, or where event loading with MEFv2s 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 (blade).
  - 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 automatically 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 blades. Each one performs tasks concurrently in a MATRIXX Engine so the workload is distributed evenly across the processing blades in an engine.
  - System Monitoring and Control
    The MATRIXX Engine is designed to be highly available and to be monitored and administered remotely. System health and performance are constantly monitored and statistics are collected on a configured interval for blade-level processes and cluster-level processes, and are stored in the statistics database.
  - Transaction Protocol Version 2
    The MATRIXX transaction protocol version 2 refers to changes in MATRIXX Digital Commerce to improve performance and reduce the resources required to run your MATRIXX Digital Commerce environment. Most of the changes are to the MATRIXX internal architecture, and are invisible to you. The few customer-visible changes are described here.
- MATRIXX Engine Data Model
  The MATRIXX Engine data model is object based. All objects are defined in XML, making them easily extendable and the in-memory databases highly configurable.
- MATRIXX Engine Modules
  The MATRIXX Engine modules run on top of the MATRIXX Engine and contain the business logic for MATRIXX Telco applications.
- MATRIXX Digital Commerce Security
  MATRIXX Digital Commerce 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.
- MATRIXX Engine High Availability and Scalability
  MATRIXX uses a combination of industry standard clustering techniques as well as a proprietary technique to achieve both high availability and high scalability within the MATRIXX Engine.
- MATRIXX Disaster Recovery (DR)
  MATRIXX Digital Commerce is designed to handle a range of possible disasters, including natural, technical, and human hazards. No decision making required during a disaster because the active engine is configured to automatically fail over to a standby engine that has the same built-in reliability and nearly-the-same transaction data.
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
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

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 (blade).

Figure 1 shows the main components of a MATRIXX processing blade. Each box represents a Linux process running on a blade server. All processes are multi-threaded and communicate asynchronously with each other by using non-blocking high speed queues. Publishing blades may also include the Event Stream Server (not pictured).

The modular design simplifies the implementation and enables functionality to be added and removed as your business needs change. All components use multiple threads to process data, which enables the engine to simultaneously rate events, generate transaction log files, integrate with external systems for subscriber management, and perform post-processing of event data.