NAP

Network Access Provider

Core Network →
Introduced in Rel-8

NAP is the entity that owns and operates the radio access network infrastructure providing wireless connectivity, which can be separate from the service provider.

Category
Core Network
Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
NAP Description Purpose Related Classification Specifications

Description

A Network Access Provider (NAP) is a logical and often legal entity within the 3GPP architecture that is responsible for providing the radio access network (RAN) infrastructure. This includes the base stations (NodeBs, eNodeBs, gNBs), the radio controllers, and the transport network connecting them to the core. The NAP owns or leases the radio spectrum and operates the equipment that establishes the initial wireless link with the User Equipment (UE). Crucially, the NAP is distinct from the Network Service Provider (NSP) or Home PLMN (HPLMN), which provides the actual subscription, authentication, and services to the end-user.

The operational relationship works as follows: When a UE attempts to attach to the network, it first connects to the radio infrastructure operated by a NAP. This NAP could be the subscriber's home operator (where NAP and NSP are the same entity) or a visited operator (in roaming scenarios). The NAP's RAN forwards the attachment request to a core network. In modern architectures, this is often facilitated by network sharing mechanisms like MORAN (Multi-Operator Radio Access Network) or MOCN (Multi-Operator Core Network). In a MOCN scenario, a single RAN (operated by one NAP) is shared and connected to the core networks of multiple NSPs. The RAN broadcasts the PLMN IDs of all supported NSPs, and the UE selects one.

The NAP's role is primarily at the Access Stratum (AS). It manages radio resource allocation, scheduling, handover execution, and the physical layer transmission/reception for the UE. From a business and signaling perspective, the NAP is identified in protocols and agreements. For billing and settlement, especially in roaming, it's critical to track which NAP provided the radio access. The distinction becomes highly relevant for Mobile Virtual Network Operators (MVNOs), who act as NSPs but do not own any RAN; they purchase bulk access from a host NAP. 3GPP specifications define interfaces and procedures (e.g., over S1, N2, X2 interfaces) that allow the NAP's RAN to communicate with potentially multiple, separate core networks operated by different NSPs.

Purpose & Motivation

The concept of a Network Access Provider was formalized to decouple the ownership of the radio network infrastructure from the provision of subscriber services. This separation addresses several economic and operational challenges in the telecommunications industry. The primary motivation is to enable new business models, most notably Mobile Virtual Network Operators (MVNOs) and extensive network sharing agreements, without requiring every service provider to invest billions in building a nationwide physical network.

Historically, operators were vertically integrated, owning both the RAN and the core network. This created high barriers to market entry. The NAP/NSP model lowers these barriers by allowing an entity (the NSP) to offer mobile services by leasing radio access capacity from an infrastructure owner (the NAP). This promotes competition and service diversity. Furthermore, in scenarios like rural coverage or new 5G deployments, the cost of building dense networks is prohibitive for a single operator. Network sharing, where one NAP builds the infrastructure and multiple operators use it, becomes economically viable. The NAP concept provides the architectural and contractual framework for this. It also clarifies roles in roaming: the visited network acts as the NAP for the roaming subscriber, providing radio access, while the home network remains the NSP, handling authentication and billing. This clear separation is essential for accurate wholesale charging and settlement between operators.

Classification

Part ofNSP
Specific typesMOCN
Related approachesMVNOPLMN

Evolution Across Releases

Rel-8 Initial

Formally defined in the context of EPS (Evolved Packet System) and network sharing enhancements for LTE. The initial architecture established the clear separation between the Network Access Provider (owning E-UTRAN) and the Network Service Provider (owning EPC). It specified mechanisms like MOCN, allowing a single eNodeB (NAP asset) to connect to multiple core networks (different NSPs).

Explore further

Broader topics and technologies where NAP plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19
TS 24.333 vj00 ProSe Management Objects for UE Configuration Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.