Home
MATRIXX 5G Integration
Charging Function
This section describes the Charging Function components and how to deploy and configure them.
Common Component Configuration Properties
This section describes properties in the MATRIXX common helm chart for CHF Standalone, CHF Diameter Adapter, NRF Client, and CHF Proxy.
Component Properties
This section describes component-specific Helm properties and values for Charging Function (CHF) applications.
Persistent Volume Properties
Kubernetes persistent volumes (PVs) are a way to manage durable storage in a Kubernetes cluster. Unlike ephemeral storage, which is tied to the life cycle of a pod, PVs offer a stable and reusable storage solution that persists beyond the lifetime of individual pods.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
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
- About MATRIXX 5G Integration
  MATRIXX 5G Integration describes how to implement the Service-Based Architecture (SBA) Gateway and messaging. In addition, this document provides information about security configuration (secured and not secured).
- MATRIXX SBA Gateway
  This section describes the Service Based Architecture (SBA) Gateway, which provides the framework to build 5G network function (NF) services based on 3GPP technical specifications.
- Charging Function
  This section describes the Charging Function components and how to deploy and configure them.
  - CHF Standalone
    CHF Standalone is an SBA Gateway implementation of the Charging Function (CHF) Network Function that uses only Backstop Processing to respond to all messages. CHF Standalone can be used to deploy and configure multiple Charging Function components, including:
  - CHF Diameter Adapter
    CHF Diameter Adapter is a MATRIXX component that converts 5G Charging Function (CHF) interface messages to 4G Diameter messages and then sends the Diameter messages to a third-party online charging system.
  - NRF Client
    NRF Client updates an external NRF on the availability of an NF service. This mirrors the default behavior of SBA Gateway. NRF Client uses the Kubernetes API to find the running pods of the NF service and queries their metrics to discover the current CPU capacity and CPU load. The total CPU capacity and average CPU load are then reported back to the NRF by updating the nfProfile it holds for the service.
  - CHF Proxy
    CHF Proxy is a MATRIXX component that routes PCF/SMF 5G network traffic to 5G charging interfaces.
  - Common Component Configuration Properties
    This section describes properties in the MATRIXX common helm chart for CHF Standalone, CHF Diameter Adapter, NRF Client, and CHF Proxy.
    - Global Properties
      5g_integration/r_chf_app_global_properties.html#reference_jlg_w4k_gyb__table_er3_5zf_2xb describes the global properties for deploying CHF Standalone:
    - Container Properties
      The chf-standalone Helm chart has properties for specifying the images for containers and checking their health and status for the CHF Standalone application.
    - Component Properties
      This section describes component-specific Helm properties and values for Charging Function (CHF) applications.
      - Deployment Properties
        You can configure properties for deployment parameters, initialization and application containers, environment variables, and resources that manage the deployment and scaling of a set of pods in your cluster. These properties define declarative updates to applications, allowing you to describe the required state for your application, and Kubernetes deploys and manages the specified number of replica pods to meet that required state.
      - Horizontal Scaling Properties
        Kubernetes horizontal scaling, also known as horizontal pod autoscaling (HPA), is a feature that allows you to adjust the number of running instances (pods) of a deployment or replica set based on the observed CPU or memory utilization. The goal is to ensure optimal resource utilization and keep a consistent level of performance for your applications.
      - Vertical Scaling Properties
        Vertical scaling in Kubernetes refers to the process of adjusting the compute resources (CPU and memory) allocated to a single instance of a containerized application running on a Kubernetes cluster. Unlike horizontal scaling, which involves adding or removing instances of an application to handle varying levels of load, vertical scaling focuses on increasing or decreasing the capacity of individual instances.
      - Job Properties
        In Kubernetes, a job is a resource type used to run pods (one or more instances of a container) to completion. It is primarily designed for short-lived, batch workloads, such as running a containerized task once or a finite number of times.
      - CronJob Properties
        In Kubernetes, a CronJob is a resource type that allows you to run scheduled tasks or jobs at specific times or intervals within your cluster. It is particularly useful for automating repetitive tasks, such as backups, data processing, or maintenance activities.
      - Service Properties
        Kubernetes services offer a way to expose and manage network access to a set of pods within a Kubernetes cluster. They offer stable endpoints and load balancing to ensure reliable communication between different components of an application regardless of the pods' life cycles.
      - Ingress Properties
        Kubernetes Ingress is an API object used to manage external access to services running within a Kubernetes cluster. It acts as a traffic manager, allowing inbound connections to reach services based on defined rules.
      - Persistent Volume Properties
        Kubernetes persistent volumes (PVs) are a way to manage durable storage in a Kubernetes cluster. Unlike ephemeral storage, which is tied to the life cycle of a pod, PVs offer a stable and reusable storage solution that persists beyond the lifetime of individual pods.
      - Configuration Map Properties
        A Kubernetes configuration map (ConfigMap) is an object that stores configuration data in key-value pairs within a Kubernetes cluster. It provides a way to decouple a configuration from containerized applications, allowing you to manage and update a configuration independently of the application code. Configuration maps are particularly useful for storing non-sensitive data, such as environment variables, command-line arguments, configuration files, or any other configuration data that your application needs.
      - Secrets Properties
        Kubernetes Secrets are a mechanism to securely store and manage sensitive information, such as passwords, OAuth tokens, and SSH keys, within a Kubernetes cluster. This approach helps ensure that sensitive data is not hard-coded or exposed in application code or configuration files.
      - Role-Based Access Control Properties
        Role-based access control (RBAC) in Kubernetes is a method for regulating access to the Kubernetes API based on the roles of individual users within the cluster. RBAC helps ensure that users and applications have the appropriate permissions to perform only the actions they are authorized to do, enhancing the security and manageability of the cluster.
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

Persistent Volume Properties

Kubernetes persistent volumes (PVs) are a way to manage durable storage in a Kubernetes cluster. Unlike ephemeral storage, which is tied to the life cycle of a pod, PVs offer a stable and reusable storage solution that persists beyond the lifetime of individual pods.

Persistent Volume Properties describes the PV properties:

Table 1. Persistent Volume Properties
Name	Description
persistence.enabled	Set this to `true` to enable persistence in the application's Helm chart. The default value is `false`.
persistance.volumes	A map of the volumes.
persistence.volumes.[name]	The name of the PV container.
persistence.volumes.[name].accessMode	The access mode for the volume. The default value is `ReadWriteOnce`.
persistence.volumes.[name].storageClass	The storage class of the volume.
persistence.volumes.[name].additionalLabels	More labels for the volume.
persistence.volumes.[name].annotations	Annotations for the volume.
persistence.volumes.[name].storageSize	The size of the volume. The default value is `8Gi`.
persistence.volumes.[name].volumeName	The name of the volume.
persistence.volumes.[name].volumeMode	The volume mode.

This is an example of a PV properties configuration:

persistence:
  enabled: true
  volumes:
    pv-volume:
      hostPath: "/tmp/data"
      accessMode: ReadWriteMany
      storageClass: "-"
      #  "helm.sh/resource-policy": keep
      storageSize: 2Gi
      volumeName: "task-pv-volume"