Home
MATRIXX Diameter Integration
Diameter Gateway
The following information describes the Diameter Gateway.
Configuring the Diameter Protocol
You can configure and customize the Diameter Dictionary and the Diameter protocol.
Extending the Diameter Dictionary
The MATRIXX Diameter Dictionary (diameter_dictionary.xml) specifies the Diameter message format and accounting services used by the Diameter applications supported by MATRIXX Engine. The specification also defines the Diameter applications, packets, AVPs, functions, AVP-to-MDC mappings, and other Diameter configurations for MATRIXX.
Copy an AVP Field Value to an MDC Field
Perform this task to copy an AVP field value to a field in the MtxDiamRoMsg MDC or any custom MDC that is based off of an MDC that exists in the Diameter dictionary.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
- About MATRIXX Diameter Integration
  MATRIXX Diameter Integration provides information about MATRIXX Engine Diameter support and configuration.
- Diameter Gateway
  The following information describes the Diameter Gateway.
  - 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.
  - Diameter Gateway Support for 5G Non-Standalone Architecture
    MATRIXX supports 5G Non-Standalone Architecture deployments by including extended fields for 5G RAN in Gx messages to enable the high-bandwidth data flows available in 5G networks.
  - Supported AVPs
    The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and contains definitions for the Diameter AVPs, functions, and Diameter-to-MDC mappings implemented in MATRIXX Engine.
  - Configuring the Diameter Protocol
    You can configure and customize the Diameter Dictionary and the Diameter protocol.
    - Diameter Protocol Configuration Parameters
      You can use the configuration parameters in create_config.py to configure the Diameter protocol implementation.
    - Decoding Diameter AVPs
      Most Diameter AVPs represent one field and its value. However, some AVPs represent multiple fields. For example, the 3GPP-User-Location-Info AVP is defined as an octet string that has many fields encoded in it. Diameter Gateway can decode specific encoded AVPs that contain more than one field.
    - Extending the Diameter Dictionary
      The MATRIXX Diameter Dictionary (diameter_dictionary.xml) specifies the Diameter message format and accounting services used by the Diameter applications supported by MATRIXX Engine. The specification also defines the Diameter applications, packets, AVPs, functions, AVP-to-MDC mappings, and other Diameter configurations for MATRIXX.
      - Required Information
        The config_engine.py script enables you to add simple AVPs, grouped AVPs, and Diameter applications to your base MATRIXX configuration. It also allows you to map MATRIXX result codes to Diameter results codes.
      - Map Functions
        Map functions change an AVP value to a different MDC field value or an MDC field value to a different AVP value. The MATRIXX Engine uses mapping functions to return results as Diameter result codes.
      - Map Conditions
        You can define zero or more conditions when mapping an MDC to a Diameter packet.
      - Add a Simple AVP to the Diameter Dictionary
        For MATRIXX Engine to recognize and process AVPs sent in the network message, they must be included in the Diameter Dictionary.
      - Add a Grouped AVP to the Diameter Dictionary
        For MATRIXX Engine to recognize and process AVPs sent in the network message, they must be included in the Diameter Dictionary. You can add grouped AVPs in which the data field is a sequence of AVPs.
      - Add a Diameter AVP to a Diameter Packet
        You can add Diameter AVPs to the following Diameter packets: AA Request, AA Answer, Accounting Request, Accounting Answer, Credit-Control Request, and Credit-Control Answer.
      - Copy an AVP Field Value to an MDC Field
        Perform this task to copy an AVP field value to a field in the MtxDiamRoMsg MDC or any custom MDC that is based off of an MDC that exists in the Diameter dictionary.
      - Diameter AVP to MDC Data Type Mapping
        When you add AVPs to your default configuration, they must be mapped to _glossary/mdc.html fields that have the correct data type for the AVP data.
    - Extending Session Objects
      Service providers can extend charging and policy session MATRIXX Data Containers (MDCs) to contain additional fields to hold provider-specific information. Fields can be added from the network message to the session to be used as the basis of normalizations during rating and policy calculations. In addition, subscriber data and custom fields in charging session objects can be used in event field maps to map incoming fields to event type MDCs so that the fields are included in the associated Event Detail Record (EDR).
    - Using Selective Updates
      Selective updates are commands that manipulate message contents at specific processing points as a message progresses through the MATRIXX Engine. They cause the system to update an MDC and perform basic transformations on the contained data.
  - Working with the Diameter Protocol
    The Diameter protocol is comprised of two basic parts: the Diameter Base Protocol and Diameter applications.
  - Handling VoLTE Announcements
    MATRIXX Engine can return Voice over Long-Term Evolution (VoLTE) Announcement-Information AVPs for Diameter LTE (Long-Term Evolution) sessions. The AVPs define the list of pre-quota announcements to play to the subscriber using VoLTE technology.
  - Handling Diameter Errors
    Errors with the Diameter protocol fall into two categories: protocol errors and application errors.
- External Diameter Gateway
  The following information describes External Diameter Gateway (EDGW).
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

Copy an AVP Field Value to an MDC Field

Perform this task to copy an AVP field value to a field in the MtxDiamRoMsg MDC or any custom MDC that is based off of an MDC that exists in the Diameter dictionary.

About this task

Perform this task on a processing server in the standby cluster.

Procedure

Use a configuration source to create a diameter_dictionary_base_xml_sed.extra file with the following content:

/<!-- extra Packet Name copy_mdc_field lines go here -->/a\<copy_mdc_field name="DestinationFieldName" source_name="SourceFieldName"/>\

Where:

Packet Name is the name of the Diameter packet (such as Accounting Request).
AvpFieldname is the name of the MDC field currently mapped to the AVP.
fieldName is the name of the MDC field to which the AVP field currently maps.
DestinationFieldName is the name of the different MDC field to map the AVP to.
SourceFieldName is the name of the MDC field representing the AVP value.

For example:

/<!-- extra Credit-Control Request copy_mdc_field lines go here -->/a\<copy_mdc_field name="TrainingDiamFld2" source_name="main.ServiceInfo.DiamPsInfo.TgppSgsnMccMnc"/>\

Important: The comment between  must be the identical to the comment in the diameter_dictionary.xml file.

For more information about configuration using a configuration source, see the discussion about configuration sources in MATRIXX Configuration.

What to do next

If the engine is not in production and is not online, follow the procedure for configuring the primary engine. If the engine is in production and is online, follow the procedure for changing the configuration of an online system.