Home
MATRIXX 5G Integration
Configuring SBA Gateway
Common Service-Based Architecture (SBA) configuration, CHF configuration, overriding default configuration options, and mapping configuration are discussed below.

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.
  - Overriding Default Network Function Configuration
    The common configuration file defines default configuration for SBA network functions. You can override those default values for your network environment.
  - Configuring Installations for Docker and Kubernetes
    The SBA Gateway, when deployed as a Docker container, can be configured at the command line or using a Docker volume in an installation for Docker and Kubernetes.
  - Common SBA Configuration
    The common SBA configuration, provided by the SBA library, defines a default configuration that is shared by every network function.
  - HTTP Client Support and Connection Negotiation
    The Java 11 native client provides HTTP/2 support to 5G network functions by default, but components can be configured to revert to the OkHttp client implementation instead. Different negotiation methods are needed depending on whether a connection is encrypted or unencrypted.
  - CHF Configuration
    The CHF configuration overrides some properties defined in gateway.yaml but only for this particular network function (CHF).
  - Mapping JSON Messages to MDC
    SBA Gateway uses OpenAPI (Swagger) specifications to validate the format of incoming JSON requests. After validation, these JSON messages are mapped to MDC structures using the Dynamic Message Mapper. This uses Mapping configuration files to map fields in the incoming JSON request to and from MDCs before sending them to and from MATRIXX Engine.
  - Routing SBA 5G Requests
    The TRA-RT requires that any MDCs submitted have sub-domain routing information provided in the MtxMsg.TrafficRouteData field.
  - NRF Client Configuration
    The Network Repository Function (NRF) section of the SBA configuration is used to register a network function with an NRF.
  - NRF Client Load and Capacity Reporting
    An NRF client can report load and capacity values to the NRF.
  - ActiveMQ Gateway Configuration
    MATRIXX Engine uses ActiveMQ to produce outbound 5G Notify requests for SBA Gateway and to consume their inbound responses.
- 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.
- 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

Configuring SBA Gateway

Common Service-Based Architecture (SBA) configuration, CHF configuration, overriding default configuration options, and mapping configuration are discussed below.

5G network functions implemented with SBA Gateway have the following configuration:

Common configuration — The common configuration is shared by every network function, is provided by the SBA library, and contains appropriate default values. These values can be overridden using the nf.yaml file or environment variables.
Function-specific configuration — A network function provides an nf.yaml configuration file with its default configuration and any overrides to the default SBA configuration.
Optional specification files — OpenAPI specification files are used for validating incoming requests. The SBA includes default API specification files.
Optional mapping configuration — For network functions such as CHF, SBA includes default mapping configuration files for mapping payloads between MDCs and JSON files.