Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Interface

N44

N44 Reference Point (NEF–CHF)

Interface →

N44 is the 3GPP reference point between the Network Exposure Function and the Charging Function, enabling charging-system interactions for exposure-related events and service usage supporting converged charging in 5G core networks.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
2 specs
N44 Description Purpose What changed Neighbours Specifications

Description

N44 is a 3GPP-defined reference point that connects the Network Exposure Function (NEF) to the Charging Function (CHF) in the 5G core network. It is specified in the charging management specifications, notably TS 32.254 and TS 32.282, which define charging principles and the charging framework for 5G system services. The NEF is the entry point for external application functions (AFs) to interact with 3GPP network services, while the CHF is the converged charging entity that collects charging information and generates charging data records (CDRs) or charging events. N44 provides the interface through which the NEF can report service usage and request charging-related operations for exposed services.

Architecturally, N44 sits within the service-based architecture (SBA) of the 5G core. The NEF exposes network capabilities to external consumers, such as application providers, and may itself consume network functions to fulfill exposure requests. When an external AF uses an exposed service that is subject to charging, the NEF must ensure that the corresponding usage is accounted for. N44 enables the NEF to communicate with the CHF using service-based interfaces, typically based on HTTP/2 and JSON as per the 3GPP SBA principles. The reference point supports charging data reporting, quota management, and event-based charging for exposure services.

The operation of N44 involves the NEF acting as a charging client or charging trigger function (CTF) for the services it exposes. When an external request is processed, the NEF generates charging events and sends them to the CHF over N44. The CHF applies rating, charging, and balance management, and may return charging decisions or quotas. This interaction ensures that exposure services—such as location reporting, quality-of-service (QoS) on demand, or event monitoring—are properly billed and that usage is recorded for both operator and third-party settlement.

N44 is closely related to other charging reference points in the 5G core, such as N40 (SMF–CHF) and N36 (PCF–CHF). While N40 handles session management charging and N36 handles policy-related charging, N44 specifically addresses the charging needs of the NEF. This separation allows the NEF to remain stateless with respect to charging data and to delegate charging complexity to the CHF. The reference point also supports converged charging, meaning that online and offline charging can be handled through the same CHF infrastructure.

In multi-vendor and roaming scenarios, N44 must be interoperable across different CHF implementations. 3GPP specifications define the message flows, data models, and error handling for N44 to ensure consistent behavior. Security is provided through TLS and OAuth-based authorization as part of the SBA security framework. As exposure services expand in 5G-Advanced and 6G, N44 is expected to remain a key interface for monetizing network capabilities.

Purpose & Motivation

N44 exists to enable charging for services exposed by the Network Exposure Function. In 5G networks, the NEF allows external applications to access network capabilities such as location, QoS, and event monitoring. These capabilities have value and must be billed, but the NEF is not itself a charging system. N44 solves this by providing a standardized interface between the NEF and the CHF, allowing the NEF to report usage and obtain charging decisions without embedding charging logic.

Before N44 was defined, exposure-related charging in earlier generations was handled through proprietary or less standardized mechanisms, often tied to specific service enablers. The introduction of N44 in Rel-17 aligns with the broader 3GPP effort to converge charging across 5G core functions and to support service-based architecture. It allows operators to monetize network exposure consistently and to integrate third-party usage into their charging and billing systems.

The reference point also supports the separation of concerns principle: the NEF focuses on exposure and API management, while the CHF focuses on rating and charging. This modularity simplifies deployment, enables multi-vendor interoperability, and supports the evolution toward network slicing and differentiated charging models. N44 is therefore a key enabler for the commercial viability of 5G exposure services.

What changed in its specifications

The latest release-to-release comparison of specifications that define N44. Each summary describes the whole specification, not only this term.

TS 32.254Rel-18 → Rel-19

CAPIF Phase 3: Adds CAPIF charging and PEC procedures, references, abbreviations, architectural text, and a CAPIF definition.

Full comparison in TS 32.254 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-17 Initial

N44 was introduced as the reference point between the NEF and CHF, enabling charging for network exposure services within the 5G service-based architecture.

The term carried over unchanged in the referenced specifications, with no revision to the definition text.

The term carried over unchanged in the referenced specifications, with no revision to the definition text.

The term carried over unchanged in the referenced specifications, with no revision to the definition text.

Defining Specifications

3GPP specifications that define or reference N44, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 read
TS 32.282 vi20 Charging management; Time Sensitive Networking Rel-18 read