Description
Core Access Network (CAN) is a concept that refers to the combined architecture of the core network and the access network, emphasizing their tight integration and interdependence in modern mobile networks. In 3GPP specifications, the term is often used in the context of network architectures that support multiple access technologies, such as 3GPP access (e.g., NR, LTE) and non-3GPP access (e.g., Wi-Fi, fixed networks).
The CAN concept is particularly relevant in the 5G System (5GS), where the core network (5GC) is designed to be access-agnostic. The 5GC supports a unified authentication framework, common policy control, and seamless mobility across different access types. The access network (AN) provides connectivity to the UE, while the core network provides services such as session management, mobility management, and policy control. The CAN encompasses the interfaces and protocols that enable communication between these domains, such as the N2 (control plane) and N3 (user plane) interfaces.
In the context of fixed-mobile convergence (FMC), the CAN concept extends to include wireline access networks, such as those defined by the Broadband Forum (BBF). 3GPP and BBF have collaborated to define the integration of 5G core with wireline access, enabling a unified core network for both mobile and fixed subscribers. This is often referred to as 5G Wireline Access (5G-WA) or Fixed Mobile Convergence.
The CAN architecture includes key components such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and the various access network elements (e.g., gNB, ng-eNB, W-AGF). The interfaces between these components are standardized to ensure interoperability and multi-vendor support. Security is also a critical aspect, with mechanisms for authentication, authorization, and encryption across the CAN.
In Release 15, 3GPP studied the integration of core and access networks, including the use of CAN for fixed-mobile convergence, as documented in TR 22.804 and TR 33.929. These studies addressed use cases, requirements, and security aspects. The work continued in Release 19 with further enhancements.
Purpose & Motivation
The CAN concept was developed to address the need for a unified, flexible, and efficient network architecture that can support diverse access technologies and service requirements. Traditional networks had separate core and access domains with limited integration, leading to inefficiencies in mobility, policy control, and service delivery. The CAN approach enables a more holistic view of the network, where the core and access work together seamlessly.
One of the primary motivations for CAN is fixed-mobile convergence. With the proliferation of high-speed fixed broadband and mobile networks, operators sought to integrate these networks to reduce costs and improve user experience. The CAN framework allows a single core network to serve both mobile and fixed access, simplifying operations and enabling new services such as converged charging and policy control.
Additionally, the CAN concept supports the 5G vision of a service-based architecture, where network functions can be deployed flexibly and scaled independently. By integrating access and core, the network can better optimize resources, improve latency, and enhance reliability. This is particularly important for emerging use cases like industrial IoT, where deterministic networking and low latency are required.
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.
Defining Specifications
3GPP specifications that define or reference CAN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.804 vg30 | 5G Automation in Vertical Domains Study | Rel-16 read |
| TS 33.929 | 3GPP TR 33.929 | Rel-15 read |