Access Network Provider

Description

The Access Network Provider (ANP) is a logical and administrative entity within the 3GPP system architecture, distinct from the Core Network Provider (CNP) and the Service Provider (SP). Its primary function is to own, manage, and operate the Radio Access Network (RAN) infrastructure. This infrastructure comprises all the physical and logical components necessary for establishing the radio connection with User Equipment (UE), including Node Bs (in UMTS), eNodeBs (in LTE), gNBs (in 5G NR), and their associated controllers like the Radio Network Controller (RNC) or Central Units (CU). The ANP is responsible for the radio resource management, handover execution, and the transmission of user and control plane data between the UE and the core network's edge.

Architecturally, the ANP operates the network segment defined by the Uu radio interface (between UE and the access node) and, typically, the Iu (for UMTS) or NG (for 5G) interface towards the core network. It does not own the subscriber data or provide end-user services like voice calls or internet packages; those are the domain of the Service Provider. Instead, the ANP provides 'bit pipe' connectivity, offering wholesale access services to one or multiple CNPs/SPs. Its operational duties include radio network planning, deployment, maintenance, optimization of cell sites, and ensuring the quality and coverage of the radio signal.

The role of the ANP becomes particularly significant in multi-operator or neutral host scenarios. For instance, in network sharing arrangements like Multi-Operator Core Network (MOCN) or Gateway Core Network (GWCN), a single ANP (which could be one operator or a third-party infrastructure company) provides RAN access to multiple core network operators. This separation allows for more efficient use of spectrum and infrastructure, reduces deployment costs, and can accelerate network coverage rollout. The ANP's performance directly impacts key user-experience metrics such as data throughput, latency, and call drop rates, as it manages the inherently scarce and variable radio resources.

From a business and standards perspective, defining the ANP clarifies responsibilities, interfaces, and billing relationships in a disaggregated telecom ecosystem. 3GPP specifications, particularly those dealing with network architecture and management (like TS 37.808), define the functional requirements and interfaces that an ANP must support to interoperate with core networks from different providers. This clear demarcation supports regulatory frameworks, enables competition, and facilitates innovations like mobile virtual network operators (MVNOs) who may not own any access network but rely entirely on an ANP for connectivity.

Purpose & Motivation

The concept of the Access Network Provider was formally introduced to address the evolving business and architectural models in the telecommunications industry, particularly the separation of network ownership from service provision. Prior to this formalization, the typical model was a vertically integrated operator that owned both the RAN and the core network, and directly provided services to end-users. This model limited flexibility, made market entry for new service providers costly (as they needed to build a full network), and could lead to inefficient duplication of infrastructure, especially in rural areas.

The ANP model was motivated by the need to enable competition, infrastructure sharing, and reduce capital expenditure (CAPEX) and operational expenditure (OPEX). By defining a clear entity responsible solely for the access layer, 3GPP standards supported the emergence of neutral host providers and network sharing agreements. This allows, for example, a company to build and operate a dense network of small cells in a stadium or airport and sell access capacity to multiple mobile network operators (MNOs), none of whom would find it economical to deploy their own infrastructure in that location.

Furthermore, this separation is a foundational principle for advanced architectural concepts like network slicing and open RAN (O-RAN). It allows the RAN resources (managed by the ANP) to be abstracted and partitioned to create virtualized, end-to-end network slices tailored for different service providers or use cases (e.g., a slice for a factory automation service managed by one SP, and a slice for public broadband managed by another). The ANP concept thus future-proofs the architecture, enabling more dynamic, efficient, and diverse business ecosystems beyond the traditional monolithic operator model.

Key Features

• Owns and operates the physical RAN infrastructure (base stations, antennas, fronthaul/backhaul)
• Manages radio resource allocation, mobility management (handovers), and connection setup/release
• Provides standardized interfaces (e.g., Iu, NG) for interconnection with one or multiple Core Network Providers
• Enables network sharing models like MOCN and GWCN to improve infrastructure utilization
• Supports neutral host scenarios, allowing third-party infrastructure providers to serve multiple operators
• Facilitates clear operational and business demarcation between access, core, and service layers

Evolution Across Releases

Defining Specifications