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

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).
- 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 Data Containers (MDCs)
    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.
  - 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 look up.
- 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 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.

How MATRIXX Transfers Data

Figure 1 shows the components that MATRIXX Digital Commerce uses to transfer and store data.

Figure 1. MATRIXX Data Model

MDCs — MATRIXX Data Containers: Used to pass information among MATRIXX components. Includes for example, processing records and results, state changes, events, and, notification messages. For more information, see the discussion about MATRIXX Data Containers.
EDRs — Event Detail Records: Represents a business event (state change to the database). Created by the Charging Servers from MDCs.

Transaction Messages: The MATRIXX Charging Server creates event objects (for billable events) and adds them to MDCs. The result is sent to the Transaction Server as a transaction message.

Events: Contain attributes unique to a chargeable occurrence. For details, see Event Streaming.

SEFs — Streamed Event Files: A temporary file created by the Event Stream Server on the MATRIXX Engine publishing server to stream events to MEFs or other locations (adds GTCs, usage, and non-usage information to EDRs).

MEFs — MATRIXX Event Files: Persistent storage for collections of events arranged in GTC order. MEF processing converts SEFs to MEFv2s. Can be published to external systems in different formats.

MATRIXX Data Objects

All database objects have a unique Object ID (OID) that can be used to efficiently locate the object in its database. Objects are linked together using their OIDs rather than actual memory addresses so an object can be relocated in the database without invalidating the links. This also allows multiple MATRIXX Engine blades to share data based on OIDs, while the actual location of the object may differ between the blades.