Home
MATRIXX 5G Integration
Creating a Mapping Configuration
The following documentation provides information on how to create a mapping configuration. For a list of MATRIXX-supported 5G messages mappings from MDC to OpenAPI, see the discussion about MATRIXX 5G message mapping.

Welcome
Release Notes
Architecture Overview
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
- About MATRIXX 5G Integration
  MATRIXX 5G Integration provides an architectural overview of how to integrate your 5G core network with the MATRIXX Digital Commerce platform. This guide also provides descriptions for the Service-Based Architecture (SBA) Gateway and messaging. In addition, this document provides information about security configuration (secured and not secured).
- 5G Standards
  MATRIXX Digital Commerce includes support for Diameter (CS networks supported with CAMEL Gateway) and SBA interface standards on a single platform.
- MATRIXX SBA Gateway Overview
  MATRIXX 5G Integration provides information about integrating MATRIXX Digital Commerce with 5G network consumers using MATRIXX Service Based Architecture (SBA) Gateway and messaging services. Upgrades and version pinning are also covered.
- Installing MATRIXX SBA Gateway
  For information about installing 5G network functions in an installation with Docker and Kubernetes, see the discussion about installing Docker in MATRIXX Cloud Native Installation and Upgrade.
- Administering the SBA Gateway
  You administer the SBA Gateway by configuring its logging and monitoring features.
- Configuring SBA Gateway
  Common Service-Based Architecture (SBA) configuration, CHF configuration, overriding default configuration options, and mapping configuration are discussed below.
- 5G Event Streaming
  SBA Gateway uses Kafka to stream HTTP requests and MATRIXX Engine HTTP responses to a Kafka broker. SBA Gateway 5G Events applications convert the received JSON to the ASN.1 binary format for export to Kafka applications.
- Creating a Mapping Configuration
  The following documentation provides information on how to create a mapping configuration. For a list of MATRIXX-supported 5G messages mappings from MDC to OpenAPI, see the discussion about MATRIXX 5G message mapping.
  - The Source Message
    The mapping configuration describes what the source message will be based upon the values for the type and the root message name.
  - The Target Message
    The mapping configuration describes what the target message will be based upon the values for the type and the root message name.
  - Validation
    You can configure the behaviour of the validation performed by the Dynamic Message Mapper. The validation can be completely disabled, which improves system performance. Validation can also be carried out in an advisory fashion (using failOnIssue: false).
  - Field Mapping
    The Dynamic Message Mapper uses the fieldMappings attribute to define the actual mappings. Underneath this is a map representing the target message structure. For each Leaf field, the Dynamic Message Mapper can specify a string value, which is a path to the source message field that will be placed in this field.
  - Sub Types
    In certain scenarios it may be beneficial to use a more specific type of object. For example, you can extend an existing MDC with additional attributes as needed for your deployment.
  - Field Value Mappers
    When setting values on the target message from the source message, it may sometimes be necessary to perform some type conversion. Multiple included FieldValueMappers can perform this conversion (for example, converting a string to an integer).
  - Input Parameters
    You can reference an input parameter instead of a field from the source message. If this is necessary, you can do so using the following syntax.
  - Output Parameters
    To produce output parameters from the mapping, you must add a top-level element in your mapping configuration called 'outputParameters'.
  - Environment Variables
    The Dynamic Message Mapper can reference environment variables when setting the default values for fields or output parameters by using the #env prefix.
  - Mapping Post Processing
    The mapping works by using a single source message field value and specifying what to do with it. This approach does not work if you need to work with multiple fields, such as the concatenation of two fields, or either A or B.
  - Groovy Mapping Post Processors
    One of the main goals of the Dynamic Message Mapper is to allow re-configuration after deployment without having to rebuild anything. Although the Java-implemented post processor allows you to add functionality after deployment, it requires some building.
  - Using MappingPostProcessor to Modify ResultCode Values
    You can use pricing specific denial codes returned by MATRIXX Engine after a ChargingDataRequest to alter the individual ResultCode in the multipleUnitInformation array.
- SBA Gateway Security
  SBA Gateway supports HTTP BASIC authentication and TLS Mutual Authentication.
- API for 5G Integration
  The URI, mapping, and OpenAPI specification are configurable, and only the HTTP method and mapping filename are not.
- Throttling
  SBA Gateway can be throttled to protect the platform against overload conditions.
- Appendixes
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

Creating a Mapping Configuration

The following documentation provides information on how to create a mapping configuration. For a list of MATRIXX-supported 5G messages mappings from MDC to OpenAPI, see the discussion about MATRIXX 5G message mapping.

A mapping configuration is read from a YAML file and contains:

Information about the source message.
Information about the target message.
Validation behaviour settings.
Information on how the target message fields must be populated.
Definitions of any non-standard field value mappers.
Output parameters and how they must be populated.
Post-mapping processors.