Home
MATRIXX 5G Integration
Charging Function
This section describes the Charging Function components and how to deploy and configure them.
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.
Heartbeat Behavior
The NRF Client sends heartbeat messages to the NRF at regular intervals. These contain any updates to the associated NRF profile as defined in the nrf.mapping.heartbeatPayload property.

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.
    - Heartbeat Behavior
      The NRF Client sends heartbeat messages to the NRF at regular intervals. These contain any updates to the associated NRF profile as defined in the nrf.mapping.heartbeatPayload property.
    - Network Function Service Query
      NRF Client queries the status of the NF service matching the selectors specified in nrf.nfServiceQuery.selectors. If any combination of label and value is a match, the metrics of that pod are queried.
    - Installing NRF Client
      The following sections describe the process and the Helm chart properties for deploying NRF Client. The procedures assume you have knowledge of and access to the kubectl tool.
    - Configuring NRF Client
      You can configure NRF Client in a Helm values file.
  - 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.
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

Heartbeat Behavior

The NRF Client sends heartbeat messages to the NRF at regular intervals. These contain any updates to the associated NRF profile as defined in the nrf.mapping.heartbeatPayload property.

In TS 29.510 of the 3GPP specification, the section on heartbeats (5.2.2.3.2) states that each heartbeat should contain an update to /nfStatus of either REGISTERED or SUSPENDED. The NRF Client updates the /capacity and /load entries from NF service pod metrics if specified in the payload.