Internal Management Service consumer

Description

An Internal MnS (Management Service) consumer is a functional entity that resides within the Public Land Mobile Network (PLMN) trust domain and consumes management services exposed by management service producers. This concept is defined in 3GPP TS 28.533 (Management and orchestration; Architecture framework) and TS 28.888 (Study on enhancement of management aspects for 5G). The PLMN trust domain refers to the secure environment owned and operated by the network operator, where all entities are trusted and authenticated. An internal MnS consumer is distinguished from an external MnS consumer, which resides outside the trust domain (e.g., a third-party application provider).

In the 3GPP management architecture, management services are provided by producers (e.g., a Network Function (NF) or a management function) and consumed by consumers. The services are exposed via standardized interfaces (e.g., MnS, which uses RESTful APIs based on HTTP/2 and JSON). An internal MnS consumer can be another management function, a network function, or an application function within the operator's domain. For example, a Self-Organizing Network (SON) function might consume performance management (PM) data from a gNB to optimize coverage and capacity. The consumer uses the service to request data, subscribe to notifications, or invoke actions.

The key characteristic of an internal MnS consumer is its location within the PLMN trust domain, which implies that it is subject to the operator's security policies and can be granted access to sensitive management data without the need for additional security gateways. This contrasts with external consumers, which may require authentication, authorization, and accounting (AAA) mechanisms and may be restricted to a subset of services. The internal consumer can also interact with other internal consumers to coordinate management actions, forming a closed-loop automation system.

Architecturally, the internal MnS consumer interacts with the management service producer through a service-based interface (SBI). The producer exposes its capabilities as a set of management services, each with defined operations and data models. The consumer discovers the producer via a service registry (e.g., the Network Repository Function (NRF) in 5G core, or a management service registry in the management plane). The communication is typically secured using TLS and may be subject to OAuth 2.0 authorization. The internal consumer must adhere to the service level agreements (SLAs) and policies defined by the operator.

The concept of internal MnS consumer is crucial for enabling autonomous network management, where multiple management functions collaborate to achieve goals such as energy efficiency, load balancing, and fault recovery. It allows for flexible decomposition of management tasks and supports the evolution towards intent-based networking, where high-level intents are translated into lower-level actions by a chain of consumers and producers. In Release 19, the definition was introduced to clarify the scope of management services and to differentiate between internal and external consumers, which is important for security and access control. Release 20 carries the same definition, indicating stability in the concept.

Purpose & Motivation

The concept of an Internal MnS consumer was created to address the need for a clear distinction between management service consumers that operate within the operator's trust domain and those that are external. In earlier management architectures, the boundaries were less defined, leading to potential security risks and ambiguity in service access. By defining internal consumers, 3GPP provides a framework for secure, efficient, and automated management within the PLMN, enabling operators to build closed-loop automation without exposing sensitive data to external entities.

The motivation stems from the growing complexity of 5G networks, which require dynamic and automated management to handle diverse services and network slicing. Management services need to be consumed by various functions within the network, such as SON, energy saving, and slice management. These functions must access management data and invoke actions in a standardized way. The internal MnS consumer concept ensures that such interactions are confined to the trusted domain, simplifying security and reducing latency.

Historically, management interfaces were often proprietary or based on legacy protocols (e.g., SNMP, CORBA). The shift to service-based management (introduced in 3GPP Release 15 and enhanced in later releases) required a new paradigm where management services are exposed as APIs. The internal MnS consumer is a key role in this paradigm, allowing management functions to be developed as microservices that can be deployed flexibly. It also supports the integration of AI/ML-based management, where analytics functions consume data and produce recommendations, all within the trust domain.