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

Glossary term · Management

External MnS consumer

External Management Service consumer

Management →

External MnS consumer is a management service consumer defined in 3GPP Release 19 as located outside the PLMN trust domain, enabling integration of external management entities with the network's management services.

Introduced
Rel-19
Where
Management
Specifications
3 specs
External MnS consumer Description Purpose What changed Neighbours Specifications

Description

The term 'External MnS consumer' refers to an entity that consumes Management Services (MnS) but resides outside the trust domain of the Public Land Mobile Network (PLMN). It was introduced in 3GPP Release 19 and is specified in TS 28.533, TS 28.579, and TS 28.888. This concept is part of the Service Based Management Architecture (SBMA) that 3GPP has adopted for management plane evolution, aligning with the Service Based Architecture (SBA) used in the 5G core network.

In the 3GPP management framework, an MnS is a set of capabilities exposed by a management service producer (typically a network function or element manager) to a management service consumer. The consumer can invoke operations to manage the network, such as configuring parameters, retrieving performance data, or receiving notifications. Traditionally, these consumers were within the same trust domain as the producer, meaning they were part of the operator's network infrastructure and subject to the same security policies. However, with the advent of 5G and the need for greater automation, external entities such as third-party application providers, vertical industry customers, or partner networks may need to interact with management services.

The External MnS consumer is defined as an MnS consumer outside the PLMN trust domain. This implies that the consumer is not inherently trusted by the PLMN and must undergo authentication and authorization before accessing management services. The trust domain concept is crucial for security; it delineates the boundary within which entities are considered trustworthy. Communications with external consumers must traverse security gateways and may be subject to additional policy enforcement, such as rate limiting, encryption, and auditing.

The integration of external MnS consumers is enabled by standardized service interfaces, such as those based on RESTful HTTP/2 protocols and specified in TS 28.533 (Management and orchestration; Architecture framework) and TS 28.579 (Management and orchestration; Procedures). TS 28.888 provides further details on the management of 5G networks, including aspects related to external exposure. These specifications define how external consumers can discover, request, and utilize management services while ensuring that the PLMN's security and integrity are maintained.

Architecturally, the external MnS consumer interacts with the management service producer through a service-based interface (SBI). The producer may be an element manager (EM), a network function (NF), or a management function (MF) within the PLMN. To support external access, the PLMN may deploy a gateway or proxy that enforces security policies and translates between external and internal protocols if necessary. The external consumer may be hosted in a different administrative domain, such as an enterprise network or a cloud environment, and may use different security credentials.

Use cases for external MnS consumers include allowing vertical industries to monitor and control network slices dedicated to their applications, enabling third-party service providers to optimize network resources for their services, and facilitating inter-operator management for roaming or network sharing. For example, a factory owner could use an external MnS consumer to adjust QoS parameters for a slice supporting industrial IoT, or a cloud service provider could request performance metrics to ensure SLA compliance.

The introduction of external MnS consumers reflects the broader trend towards openness and programmability in 5G networks. It allows operators to monetize their management capabilities by exposing them to partners and customers, while maintaining strict security controls. However, it also introduces challenges related to security, privacy, and interoperability, which are addressed by the 3GPP specifications through mechanisms like OAuth 2.0-based authorization, TLS encryption, and audit logging.

In summary, the External MnS consumer is a key enabler for the exposure of management services to external entities in a secure and standardized manner. It is a relatively recent addition to the 3GPP management framework, reflecting the evolving needs of 5G and beyond for flexible, multi-party management interactions.

Purpose & Motivation

The External MnS consumer concept was created to address the growing need for external parties to interact with mobile network management systems in a secure and standardized way. In traditional 2G, 3G, and early 4G networks, management was strictly an internal operator function, with no exposure to outside entities. However, with the advent of 5G and its promise of network slicing, edge computing, and industry verticals, operators recognized that external stakeholders—such as enterprises, application providers, and partners—need visibility and control over the network resources that serve them. This need is particularly acute in scenarios like private 5G networks, where an enterprise may own and operate parts of the network, or in network slicing, where a slice customer may want to monitor and adjust slice performance.

The concept of a trust domain is central to this purpose. The PLMN trust domain encompasses all entities that are under the operator's administrative control and adhere to its security policies. External entities are outside this domain and therefore cannot be automatically trusted. The External MnS consumer definition provides a clear architectural boundary and security paradigm: any consumer outside the trust domain must be explicitly authenticated, authorized, and subjected to additional security measures. This allows operators to safely expose management services without compromising the integrity of their networks.

Before the introduction of this term, there was no standardized way to refer to or handle external management service consumers. Early attempts at exposure were proprietary or limited to specific interfaces, leading to interoperability issues and security risks. The definition in Release 19, along with the associated specifications, provides a common language and framework for industry players to develop compatible solutions. It also aligns with the 3GPP's overall vision of a service-based management architecture that can flexibly serve both internal and external needs, thereby unlocking new business models and operational efficiencies.

What changed in its specifications

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

TS 28.533Rel-18 → Rel-19

Rel-19 adds Annex A.11, an illustrative architecture reference model in which management functions produce and/or consume Management Services. It also defines internal and external MnS consumers by PLMN trust domain.

Full comparison in TS 28.533 →

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

Initial definition: 'an MnS consumer outside the PLMN trust domain.' This established the concept of external management service consumers and their security implications.

The definition was slightly reworded to 'MnS consumer outside the PLMN trust domain.' The change removes the article 'an' and capitalizes 'MnS', but the meaning remains the same. This is a minor editorial change.

Defining Specifications

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

SpecificationTitleRelease
TS 28.533 vk10 5G Management Architecture Framework Rel-20 read
TS 28.579 vj00 Management Services Exposure via CAPIF Rel-19 read
TS 28.888 vk00 Enhanced Exposure of Management Services Rel-20 read