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

Glossary term · Management

NPN-SC

NPN Service Customer

Management →

NPN-SC is a Non-Public Network Service Customer role in 3GPP management specifications, representing the entity that consumes NPN services from an NPN operator and enables clear separation of service consumption and network operation.

Introduced
Rel-18
Where
Management
Specifications
2 specs
NPN-SC Description Purpose Neighbours Specifications

Description

NPN Service Customer (NPN-SC) is a role defined in 3GPP management specifications TS 28.828 and TS 28.907 within the Non-Public Network (NPN) management framework. The NPN-SC is the entity that consumes services provided by an NPN Operator (NPN-OP). This role separation is fundamental to the 3GPP management architecture for NPNs, where the organization that uses the private network may differ from the organization that operates it.

In practice, an NPN-SC could be an industrial enterprise that requires a private 5G network for factory automation, a campus operator needing dedicated connectivity, or a venue owner requiring localized high-performance coverage. The NPN-SC interacts with the NPN-OP through standardized management services to request, configure, and monitor the NPN services it consumes. These services may include connectivity for specific devices or groups, network slice instances in a PNI-NPN deployment, performance and fault reports, and configuration of access control parameters.

The management specifications define the information model and service interfaces that support the NPN-SC role. The NPN-SC can request service provisioning, specify requirements such as coverage areas, device groups, and QoS characteristics, and receive assurance data. In a PNI-NPN scenario, the NPN-SC's requirements are translated by the NPN-OP into network slice and closed access group configurations within the public network. In an SNPN scenario, the NPN-SC consumes services from the dedicated standalone network operated by the NPN-OP.

The role separation enables flexible business models. An enterprise might own the spectrum and infrastructure but contract a third party as NPN-OP to manage it, while the enterprise itself acts as NPN-SC. Alternatively, a public operator might act as NPN-OP, providing a network slice to an enterprise that acts as NPN-SC. The standardized interfaces ensure that management systems from different vendors can interoperate, supporting automation of service requests and assurance reporting.

Understanding NPN-SC is important for designing and implementing NPN management solutions because it defines the boundary between service consumption and network operation. This boundary enables clear accountability, supports multi-tenancy, and allows enterprises to focus on their business applications while relying on specialized operators for network management. The NPN-SC role, together with NPN-OP, forms the core of the 3GPP NPN management model introduced in Release 18.

Purpose & Motivation

The NPN-SC role was created to address the need for clear service consumption semantics in private 5G networks. Traditional public network management assumed the operator and the user were distinct but did not model the rich business relationships found in NPN deployments, where an enterprise may consume network services without operating the network, or may operate infrastructure shared with other parties. Without a standardized customer role, service requests, assurance reporting, and SLA management would rely on proprietary interfaces.

By defining NPN-SC in TS 28.828 and TS 28.907, 3GPP enables standardized management interactions between the entity consuming NPN services and the entity operating the network. This supports automation: an enterprise's management system can programmatically request connectivity for new device groups, adjust QoS requirements, or retrieve performance reports through standardized APIs. It also supports multi-party business models where infrastructure ownership, operation, and consumption are separated.

The NPN-SC concept also facilitates PNI-NPN deployments, where the customer's requirements must be mapped onto network slices and closed access groups managed by a public operator. By formalizing the customer role, 3GPP ensures that the requirements and expectations of service consumers are explicitly represented in the management architecture, improving clarity, accountability, and interoperability across the NPN ecosystem.

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

The NPN-SC role was introduced in Release 18 in TS 28.828 and TS 28.907, defining the service customer entity and its management interactions with the NPN Operator. This established the foundational role separation for NPN service consumption and provisioning.

The term carried over into Release 19 with the same definition text ('NPN Service Customer') in TS 28.828 and TS 28.907; the available wording shows no change to the definition itself, though surrounding management capabilities may have been extended.

Defining Specifications

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

SpecificationTitleRelease
TR 28.828 vi00 Charging Aspects for Non-Public Networks Rel-18 read
TR 28.907 vj00 Enhanced Management of Non-Public Networks Rel-19 read