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

Glossary term · Core Network

LAC

L2TP Access Concentrator

Core Network →

LAC is the network function that terminates L2TP tunnels from user equipment and aggregates their traffic for forwarding into a packet data network.

Introduced
R99
Where
Core Network › 5G Core
Specifications
19 specs
Also in
Radio Access Network, Services, Management
LAC Description Purpose What changed Neighbours Specifications

Description

The L2TP Access Concentrator (LAC) is a network element defined within 3GPP architectures for scenarios involving Layer 2 Tunneling Protocol (L2TP). Its primary role is to act as an initiator and terminator of L2TP tunnels on the network side, facilitating a user's access to packet data services. In a typical architecture involving mobile access, the User Equipment (UE) establishes a Point-to-Point Protocol (PPP) session. The LAC, often co-located with or interfacing the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW) in earlier 3GPP releases, terminates this PPP session and encapsulates the PPP frames within L2TP tunnels.

Operationally, the LAC works in conjunction with an L2TP Network Server (LNS). The LAC is responsible for the tunnel setup and maintenance procedures with the LNS, as defined in IETF RFC 2661 and later updates. It forwards the user's PPP frames through the secure L2TP tunnel to the LNS, which then de-encapsulates them and injects the IP traffic into the target Packet Data Network (PDN). The LAC handles the aggregation of multiple user sessions into a smaller number of tunnels towards the LNS, optimizing network resource usage. It also plays a role in authentication, often participating in CHAP or PAP exchanges by proxying authentication messages between the UE and the LNS or a RADIUS server.

Within the 3GPP network architecture, the LAC is a key component for enabling certain access types and interworking scenarios. It was particularly relevant for dial-up and DSL interworking, where mobile networks needed to provide seamless access to corporate intranets or ISP services that relied on PPP-based authentication and addressing. The LAC resides in the visitor or home network and provides the interface between the 3GPP packet core and non-3GPP, PPP-based access networks, ensuring secure and managed connectivity for roaming and fixed-mobile convergence use cases.

Purpose & Motivation

The LAC was introduced to solve the problem of integrating 3GPP mobile networks with existing corporate and Internet service provider (ISP) infrastructures that were built around PPP and L2TP technologies. Prior to ubiquitous native IP connectivity in mobile devices, many remote access solutions for enterprises used dial-up networks with PPP. The purpose of the LAC was to allow a mobile device to emulate a dial-up client, connecting via the 3GPP packet core to a corporate LNS, thereby providing secure, private network access without requiring changes to the corporate firewall and authentication servers.

Its creation was motivated by the need for interworking and service continuity during the evolution from 2G/3G to all-IP cores. It addressed the limitation of early mobile data services, which lacked the sophisticated secure tunneling and authentication mechanisms required by enterprises. By implementing L2TP termination in the network, operators could offer a value-added 'mobile VPN' service. This technology bridged the gap between the evolving mobile packet core and the entrenched legacy remote access infrastructure, facilitating business adoption of mobile data. It provided a standardized method for tunneling and user session management that was independent of the underlying radio access technology (GERAN, UTRAN).

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.221Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.221: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.221 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced the LAC as part of the 3GPP packet core architecture for interworking with external PDNs. This release specified its role in the context of the GGSN, defining how it terminates mobile-originated PPP sessions, establishes L2TP tunnels with a corporate LNS, and facilitates secure access to enterprise networks. It laid the groundwork for mobile VPN services.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 25.201 vj00 UTRA Physical Layer General Description Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.302 vj00 UTRA Physical Layer Services Rel-19 read
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TS 25.467 vj00 UTRAN Architecture for 3G Home Node B Rel-19 read
TR 25.967 vj00 Home NodeB RF Requirements Technical Report Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read