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

Glossary term · Management

EGMF

Exposure Governance Management Function

Management →

EGMF is a Rel-18 management function that governs network capability exposure to external and internal consumers by enforcing policy, authorization, and lifecycle control over exposure services in 5G-Advanced core networks.

Introduced
Rel-18
Where
Services
Specifications
2 specs
EGMF Description Purpose Neighbours Specifications

Description

The Exposure Governance Management Function (EGMF) is a Rel-18 functional entity introduced within the 3GPP management and exposure architecture to provide centralized governance over the exposure of network capabilities. In 5G systems, exposure is realized through the Network Exposure Function (NEF) and related entities such as the Service Enabler Server (SCEF) and the Network Data Analytics Function (NWDAF). As the number of exposure services, APIs, and consuming application functions grew, operators needed a consistent way to control who may expose what, to whom, under which conditions, and for how long. The EGMF addresses this need by acting as the policy decision and lifecycle management point for exposure.

Architecturally, the EGMF sits in the management domain and interacts with exposure functions and with the business support systems. It maintains governance policies that define exposure scope, allowed consumer categories, data sensitivity constraints, consent requirements, and rate or quota limits. When an exposure function intends to publish a new service or API, or when a consumer requests access, the exposure function consults the EGMF for an authorization decision. The EGMF evaluates the request against the stored policies and returns a decision together with obligations such as logging, anonymization, or time-bound access. The EGMF also manages the lifecycle of exposure services, including registration, approval, versioning, suspension, and retirement.

The function relies on a policy repository and a governance data model. Policies can be expressed at different granularities: per service, per consumer, per data type, or per network slice. The EGMF exposes its own management services so that operations support systems and authorized administrators can create, modify, and audit policies. Audit trails are a core output, since regulators and internal compliance teams require evidence that exposure of sensitive data, such as location or subscription information, was properly authorized.

The EGMF is closely tied to the broader 3GPP exposure framework described in 23.435 and the study in 23.700. It complements, rather than replaces, the NEF: the NEF handles the actual protocol-level exposure and API invocation, while the EGMF provides the governance layer above it. This separation of concerns allows exposure functions to remain lightweight and focused on API mediation, while policy, consent, and compliance logic is centralized and consistently applied across all exposure channels.

In deployment, the EGMF may be realized as part of an operations support system, as a standalone management function, or as a capability within a larger exposure governance platform. Its decisions influence both the control plane, through authorization of exposure requests, and the management plane, through lifecycle and policy management. Because exposure is increasingly used for network slicing, edge computing, and IoT services, the EGMF plays a growing role in ensuring that monetization of network capabilities remains compliant and controllable.

Purpose & Motivation

Before the EGMF, exposure control in 5G networks was fragmented. Each exposure function, such as the NEF or individual enabler servers, applied its own authorization logic, and operators had no single point to define and audit exposure policy. This led to inconsistent treatment of sensitive data, difficulty proving regulatory compliance, and slow onboarding of new exposure services because each had to be individually vetted.

The EGMF was created to solve these problems by separating governance from mediation. It provides one authoritative place to define who can expose which capabilities, to which consumers, under which constraints, and for how long. This makes exposure auditable, reduces the risk of unauthorized data disclosure, and accelerates the rollout of new APIs because policy can be reused across services.

The function also responds to the commercial reality of 5G-Advanced, where exposure is a primary monetization channel. Operators need to package and govern capabilities such as location, QoS, and edge computing for many partners. The EGMF gives them the tooling to do so consistently, with consent management and lifecycle control built in, rather than bolted onto each exposure silo.

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-18 Initial

Initial introduction of the Exposure Governance Management Function as a management-layer entity for governing capability exposure, with policy-based authorization, lifecycle control, and audit capabilities defined in the 23.435 and 23.700 context.

The term carried over unchanged in its core definition; Rel-19 work continued to reference the EGMF within the evolving exposure governance architecture without redefining the function itself.

The term carried over unchanged; the EGMF remains the governance anchor for exposure as later releases extend exposure to new capability domains.

Defining Specifications

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

SpecificationTitleRelease
TS 23.435 vk00 Network Slice Capability Enablement (NSCE) Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read