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 is a highly scalable real-time event-processing solution built on patented Parallel-MATRIXX™ and Algebraic-Decision technologies. It combines efficient, transactional event processing with a highly flexible pricing, rating, policy, and aggregation engine. It performs transactional rating and charging for communications and media products and services, policy decision making based on traffic-type criteria, and event aggregation for usage analysis.

MATRIXX provides converged web and Telecom services, including voice, video, messaging, and data content services. It supports traffic session control protocol (SCP) fixed networks, mobile networks, and next generation network/IP multimedia subsystem (NGN/IMS) networks, such as transaction capabilities application part (TCAP), CAMEL application part (CAP), session interface protocol (SIP), and Diameter, and provides integrated call control capabilities. The base platform, MATRIXX Engine, provides extensive real-time balance management, subscriber management, session management, and event processing capabilities.

To create a solution that satisfies your charging and policy requirements, you configure business-logic modules into MATRIXX Engine, such as with MATRIXX Charging Application and MATRIXX Policy Application. In this configuration, MATRIXX Charging Application functions as a charging system and MATRIXX Policy Application functions as a policy and rules system. The underlying MATRIXX Engine provides the transaction processing foundation into which business logic in the form of modules can be plugged for event processing.

MATRIXX Engine runs its software components in Kubernetes pods, either on-premises or in a public cloud environment.

Online charging, policy, and call control require handling real-time critical events where low and predictable latencies are required. To ensure MATRIXX Engine is processing transactions consistently at peak performance, all operations not related to event processing are handled by a publishing pod.

The processing pod runs the business logic related to real-time critical event processing, such as network authentications, policy rules, charging and rating, notifications, and subscriber care operations. As network messages are received and transactions processed, the in-memory databases are updated and the transactions are logged to disk and sent to the secondary engine for replay.

The active publishing pod archives transaction log files published by the processing pods, creates database checkpoints, and generates MATRIXX Event Files (MEF). The standby publishing pod processes transactions and keeps the in-memory database up-to-date, so if a failover occurs, it can recover all processed events. If the optional Event Streaming Framework is enabled, both the active and standby publishing pods create internal event files to aid in a fast recovery.

See the discussion about MATRIXX overview for information about each component.