Home
MATRIXX Architecture
MATRIXX Engine Modules
The MATRIXX Engine modules run on top of MATRIXX Engine and contain the business logic for MATRIXX Telco applications.
MATRIXX Gateways
The MATRIXX gateways are interfaces between the MATRIXX Engine and external systems.
CAMEL Gateway
The CAMEL Gateway is a TCAP server that allows communication between MATRIXX Engine and a network entity.

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.
- 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 Gateways
    The MATRIXX gateways are interfaces between the MATRIXX Engine and external systems.
    - External Diameter Gateway Overview
      External Diameter Gateway (EDGW) is a cloud native Diameter gateway that enables communication for the Rf, Gz, Gy / Ro, Gx, Rx, and Sy Diameter interfaces. It runs as a stateless pod and converts Diameter protocol messages to MDCs that are sent to MATRIXX Engine.
    - Diameter Gateway Overview
      Diameter Gateway is a Diameter server that allows communication between MATRIXX Engine and a network entity requesting service through the Diameter protocol.
    - MDC Gateway
      The MDC Gateway conducts the internal exchange of data between MATRIXX servers and external exchange of subscriber management data with other MATRIXX gateways and web apps.
    - ActiveMQ Gateway
      The ActiveMQ Gateway is part of the MDC Gateway that communicates with Apache ActiveMQ.
    - CAMEL Gateway
      The CAMEL Gateway is a TCAP server that allows communication between MATRIXX Engine and a network entity.
    - REST Services (RS) Gateway
      RS Gateway provides an easy integration point for external REST clients and Java applications to make API calls to MATRIXX Engine.
    - TM Forum (TMF) Gateway
      The TMF Gateway implements the set of TMF microservice APIs supported by MATRIXX.
  - MATRIXX Normalization Module
    The Normalization module is responsible for validating the incoming request data and performing any operator-specific normalization of the data. It is integrated with the MATRIXX Charging Application and the MATRIXX Policy Application.
  - MATRIXX Application Module
    The Application module implements MATRIXX Charging Application and MATRIXX Policy Application and is responsible for the core business logic associated with a given solution.
  - MATRIXX Enrichment Module
    The Enrichment module adds additional data to a processed event, a response message, or both. It is integrated with the Charging Server.
- 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

CAMEL Gateway

The CAMEL Gateway is a TCAP server that allows communication between MATRIXX Engine and a network entity.

The CAP protocol provides a framework for access technologies that require routing and charging support across mobile networks. Many GSM mobile networks use this protocol for real-time charging of voice calls.

The external Global System for Mobile Communications (GSM) and Mobile Switching Center (MSC) communicate with MATRIXX Engine using the CAP protocol to charge for voice calls or SMS messages. When a network message is received, the CAMEL Gateway translates the data from the CAP protocol format into MATRIXX Data Containers (MDCs), which provides the time-based reservation functionality for charging voice calls. The translation includes mapping CAP message attributes to MDC fields. The attributes supported include called and calling numbers, network element addresses, and other fields required to supply rating and charging information for a voice call. The mapping is based on the message type, and MATRIXX Engine configuration format is XML, so it is easy to support additional information or modify existing information.

When a voice call is set up by the network, an initial message (IDP) is sent to the CAMEL Gateway, which converts the message contents into MDC format and sends the request to MATRIXX Charging Application. After processing the MDC and converting it to the relevant TCAP message, for example, TCAP CONTINUE(ApplyCharging), MATRIXX Charging Application sends the TCAP message back to the CAMEL Gateway for return to the originating network element, which is typically an MSC.