Intent Handling Function

Description

The Intent Handling Function (IHF) is a functional entity defined within the 3GPP management framework, primarily specified in TS 28.312 (Intent driven management services for mobile networks) and studied in TR 28.883. It sits between intent owners — such as communication service providers, vertical industry customers, or network operators — and the underlying management services that control network resources. Its fundamental role is to take an intent, which is a declarative, technology-agnostic expression of a desired outcome (for example, 'provide at least 100 Mbit/s throughput to all subscribers in this factory campus during production hours'), and convert it into actionable, machine-consumable management operations.

Architecturally, the IHF is part of the intent-driven management framework that builds on the service-based management architecture (SBMA) of 3GPP. Intent owners interact with the IHF through an intent management service (IntentMnS) exposed via standardized service APIs. Inside the IHF, several logical functions cooperate: an intent translation function that maps intent expectations to measurable requirements and policies; a conflict resolution function that detects and resolves contradictions between multiple intents; a feasibility check function that validates whether the current network capabilities can satisfy the expressed expectations; and an intent monitoring function that continuously tracks fulfillment and triggers corrective actions when deviations occur. The IHF may also interact with policy frameworks (such as the PCRF/PCF domain through management-plane interfaces) and with the intent-driven management capabilities embedded in RAN and core network management entities.

The IHF operates across multiple levels of the management hierarchy. At the top, a business-level IHF can handle customer or service-level intents that are essentially commercial or experiential. These are decomposed and delegated to lower-level IHFs responsible for specific technology domains such as radio access, transport, or core network. This hierarchical federation allows scaling and domain-specific optimization while maintaining a single, consistent intent lifecycle. The IHF maintains an intent state model — typically expressed as intent expectations with associated targets, context conditions, and validity periods — and reports fulfillment status back to the intent owner through standardized notifications. When network conditions change (for example, due to load fluctuations or failures), the IHF re-evaluates the intent and re-optimizes the corresponding policies.

Key to the IHF concept is the separation of 'what' from 'how'. The intent owner specifies the desired outcome and constraints, not the detailed configuration. The IHF, together with associated decision-making entities such as the Management Data Analytics Function (MDAF) and AI/ML-based control loops, determines the 'how'. This requires the IHF to use models, analytics, and possibly machine learning to reason about network behavior. The IHF also manages intent lifecycle states: creation, activation, evaluation, fulfillment or violation, modification, and deactivation. It supports intent reporting, so operators can audit how intents influenced the network. Security and trust are critical: the IHF must authenticate and authorize intent owners and ensure that malicious or erroneous intents cannot destabilize the network.

In Release 20, the IHF is a normative component of the intent-driven management services specified in TS 28.312, with study material in TR 28.883 detailing use cases such as network slicing, energy efficiency, and RAN optimization. The IHF enables a shift from imperative, manual management to autonomous, goal-oriented operations, which is essential for the zero-touch network and service management vision of 5G-Advanced and future 6G systems. It integrates with network slicing management, allowing slice-related intents to be translated into slice subnet and network slice instance policies, and with closed-loop assurance to continuously meet service-level objectives.

Purpose & Motivation

The IHF was created to solve a fundamental scalability and complexity problem in mobile network management. Traditional management relies on human operators translating high-level business goals into thousands of low-level configuration parameters across RAN, transport, core, and cloud domains. This is slow, error-prone, and cannot keep pace with the dynamic requirements of 5G and beyond, such as on-demand network slicing, ultra-low-latency services, and rapidly changing traffic patterns. Intent-based management, enabled by the IHF, allows operators to express goals declaratively and let the management system determine the necessary actions, reducing operational expenditure and enabling autonomous operation.

Before the IHF, 3GPP management architecture focused on provisioning and policy-based control, but lacked a standardized way to handle high-level intents with closed-loop fulfillment and conflict resolution. Vendor-specific automation solutions existed but were not interoperable, making multi-vendor, multi-domain intent management difficult. The IHF standardizes the intent lifecycle, data models, and service interfaces, so that intents can be created, monitored, and assured across heterogeneous network domains. It also provides a foundation for AI/ML-driven management, as required by the 3GPP vision of zero-touch networks and the emerging 6G management architecture.

The IHF addresses previous limitations by introducing formal intent models, conflict detection, feasibility assessment, and continuous assurance. It enables business-to-network alignment: a business goal (e.g., 'improve customer experience in this region') can be automatically translated into network actions without manual parameter mapping. This is essential for network slicing, where multiple tenants with different intents share the same infrastructure, and for energy efficiency, where intents balance performance against power consumption.