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 Components Overview
Figure 1 shows the core components that you configure to process network traffic. Traffic Routing Agents (TRAs) load balance network traffic to a MATRIXX Engine, the heart of a MATRIXX implementation. The Business API Gateway, SBA Gateway,TRA, and MATRIXX Engine architecture are described in more detail in the sections that follow.
A MATRIXX 5G environment accepts traffic into the SBA Gateway, which is a 5G Charging Function (CHF). The SBA Gateway converts outside traffic into MATRIXX Data Containers (MDCs) that other MATRIXX components use to communicate.
Note: 5G components run in
Kubernetes only. For information about using 5G components, refer to the cloud native documentation.
From an event processing perspective, a MATRIXX Engine consists of the MATRIXX processes and services required to
accept network and BSS messages and convert them to events. You can then rate and charge the events, optionally apply policy rules triggered by the event, or both. A MATRIXX Engine is made up of two or three processing servers, two publishing servers, a checkpointing pod, and shared storage (a SAN device). The processing servers accept incoming messages, and use the Charging Server to turn them into events (Event Detail Records (EDRs). Events can
then be transmitted as data structures for further processing, or stored as event objects. The checkpointing pod
creates database checkpoints. The processing servers, publishing servers, checkpointing servers, and shared storage are described in more detail in the sections that follow.
Note: See
MATRIXX Event Streaming for a discussion about other components that event streaming uses and
how they fit into a MATRIXX implementation. For information, see the discussion about
EDRs in MATRIXX Integration.
