From LTE to 5G: How ORAN Is Reshaping the Future of Wireless Networks
1. Introduction: Why the LTE-to-5G Journey Matters
The wireless telecommunications industry is in the midst of the most significant architectural shift it has seen since the rollout of 4G LTE a decade ago. We are no longer simply upgrading data speeds — we are fundamentally reimagining how radio access networks are built, operated, and who controls them.
At the centre of this transformation is a trio of interconnected forces: LTE (Long Term Evolution) as the existing backbone of mobile connectivity worldwide, 5G NR (New Radio) as the next-generation air interface, and ORAN (Open Radio Access Network) as the architectural philosophy that enables multi-vendor, software-driven, disaggregated networks.
Understanding how these three fit together is no longer optional knowledge for telecom engineers — it is foundational. Whether you are a protocol tester, network designer, or RF engineer, the LTE-to-5G-ORAN story defines the technology landscape you are working in right now.
2. The LTE Foundation - What Makes 4G Still Relevant
LTE, standardised under 3GPP Release 8, was built on a clean-slate architecture called the Evolved Packet System (EPS). Its key contribution was the separation of control plane and user plane at the core level, combined with a flat, all-IP radio access network that eliminated legacy circuit-switched complexity.
The LTE radio interface introduced several innovations that are still foundational today:
- OFDMA on the downlink — Orthogonal Frequency Division Multiple Access enables efficient multi-user scheduling across Physical Resource Blocks (PRBs)
- SC-FDMA on the uplink — Single-Carrier FDMA reduces UE power consumption while maintaining spectral efficiency
- MIMO antenna systems — From 2×2 to 4×4 configurations for spatial multiplexing and diversity gain
- Carrier Aggregation (CA) — Introduced in LTE-A (Release 10), allowing up to 5 component carriers to be aggregated for peak throughputs
- Advanced protocol stack — PHY, MAC, RLC, PDCP, and RRC layers with HARQ, ARQ, and robust QoS control
What makes LTE especially relevant today is its role as the control plane anchor in 5G NSA deployments. The eNodeB does not retire when 5G arrives - it becomes the LTE anchor that manages signalling while the 5G NR gNB handles the high-speed user plane. This is the EN-DC (E-UTRA NR Dual Connectivity) mode that most operators launched 5G with.
3. 5G Deployment Modes: NSA vs SA and the LTE Anchor Role
When operators began rolling out 5G, they faced a fundamental deployment question: build a standalone 5G core from scratch, or lean on the existing LTE infrastructure to accelerate time-to-market? The answer produced two distinct deployment architectures defined in 3GPP specifications.
Non-Standalone (NSA) -Option 3x
In the NSA mode, the 5G NR gNB acts as a secondary node while the LTE eNB serves as the master node (MN). The LTE eNB maintains the control plane connection to the 4G EPC, while the NR gNB adds additional user plane capacity through EN-DC. The UE is simultaneously connected to both nodes, delivering higher peak throughputs without requiring a new 5G Core (5GC).
Standalone (SA) - Option 2
SA mode is the target architecture for true 5G. Here, the NR gNB connects directly to the 5G Core (5GC), which introduces the AMF (Access and Mobility Management Function), SMF (Session Management Function), and UPF (User Plane Function) — replacing the legacy MME/SGW/PGW split. SA enables full 5G capabilities including network slicing, ultra-low latency, and native edge computing.
4. What is ORAN? Breaking Open the Radio Access Network
For most of 4G LTE history, the Radio Access Network was a black box. Operators purchased integrated base station solutions from a single vendor — hardware, software, interfaces, and management - all locked in a proprietary package. Swapping vendors meant ripping out and replacing entire deployments.
ORAN (Open Radio Access Network) defines a set of open interfaces and architecture principles that allow operators to mix and match radio units, baseband processing, and software from different vendors - just as they do in the IT world.
- Hardware and software disaggregation - run baseband software on commercial off-the-shelf (COTS) hardware
- Open fronthaul interfaces - standardised eCPRI-based fronthaul between O-RU and O-DU replaces proprietary CPRI
- Intelligent network control -the RAN Intelligent Controller (RIC) enables AI/ML-driven real-time and near-real-time optimisation
- Multi-vendor interoperability - operators can select best-of-breed components and avoid single-vendor dependency
- Cloud-native deployment - O-DU and O-CU can run as containerised functions in a cloud infrastructure (vRAN/Cloud RAN)
5. ORAN Architecture: O-RU, O-DU, O-CU and the RIC
The ORAN Alliance has defined a clear functional decomposition of the gNB into three logical units, each with standardised interfaces between them.
ORAN Functional Architecture ┌─────────────────────────────────────────────┐ │ SMO (Service Management & │ │ Orchestration Framework) │ │ ┌──────────────────────────────┐ │ │ │ Non-RT RIC (Non-Real-Time) │ │ └─────────┼──────────────────────────────┼────┘ │ A1 Interface │ ▼ │ ┌──────────────────────┐ │ │ Near-RT RIC │◄── E2 ──────────┘ │ (xApps run here) │ └──────────────────────┘ │ E2 interface ┌─────────▼──────────────────────┐ │ O-CU (Central Unit) │ │ O-CU-CP | O-CU-UP │ │ (RRC/PDCP-C | PDCP-U) │ └─────────────┬──────────────────┘ │ F1 Interface ┌─────────────▼──────────────────┐ │ O-DU (Distributed Unit) │ │ (RLC / MAC / High-PHY) │ └─────────────┬──────────────────┘ │ Open Fronthaul (eCPRI / 7.2x split) ┌─────────────▼──────────────────┐ │ O-RU (Radio Unit) │ │ (Low-PHY + RF Transceiver) │ └────────────────────────────────┘ │ ───────── UE (User Equipment)O-RU -Radio Unit
The O-RU handles the RF transceiver functions and the low-PHY layer. It performs digital beamforming, IQ sample processing, and the time-sensitive portions of the physical layer. It connects to the O-DU via the Open Fronthaul interface based on eCPRI, which replaced the older proprietary CPRI.
O-DU — Distributed Unit
The O-DU handles the high-PHY, MAC, and RLC layers. It performs scheduling, HARQ processing, encoding/decoding, and radio resource management. Latency constraints at the DU are strict — fronthaul transport latency must be kept below 100 µs for 7.2x functional split.
O-CU - Central Unit
The O-CU handles the upper layers: PDCP and RRC. It is split further into O-CU-CP (control plane — handling RRC and PDCP-C) and O-CU-UP (user plane — handling PDCP-U). The F1 interface connects O-CU to O-DU, while the E1 interface separates the CP and UP within the CU.
The RAN Intelligent Controller (RIC)
The RIC is perhaps the most transformative element of ORAN. It introduces a programmable intelligence layer with two tiers:
- Near-RT RIC — operates with 10 ms to 1 s control loops, runs xApps that perform per-UE decisions like handover optimisation, load balancing, and interference mitigation
- Non-RT RIC — operates with >1 s loops, part of the SMO framework, runs rApps for AI model training, policy management, and long-term optimisation
6. How LTE Fits Inside the ORAN Ecosystem
A common misconception is that ORAN is purely a 5G concept. In practice, ORAN principles apply to LTE networks as well, and many operators are building converged ORAN platforms that support both LTE and 5G NR from the same infrastructure.
Several deployment models describe how LTE integrates with ORAN:
LTE as the NSA Anchor in an ORAN-based 5G Network
In an NSA deployment built on ORAN infrastructure, the LTE eNB may be virtualised and managed through the SMO framework. The O-CU can terminate both the LTE RRC (serving as the MN-leg) and the NR RRC (serving as the SN-leg) in an EN-DC configuration, with policy control managed through the Near-RT RIC.
Converged O-DU Supporting LTE and NR
Some ORAN vendor implementations support a converged O-DU that simultaneously runs both the LTE PHY/MAC stack and the 5G NR PHY/MAC stack, sharing a common fronthaul interface to a dual-mode O-RU. This allows operators to run LTE and 5G on the same physical hardware under the same ORAN management framework.
LTE Traffic Offload and Steering via the RIC
The Near-RT RIC can run xApps that make cross-technology steering decisions — deciding whether to serve a UE on LTE or hand it to 5G NR based on traffic type, signal quality, QoS requirements, and load conditions. This intelligent inter-RAT management is one of ORAN's key operational advantages.
7. Challenges in the LTE-to-5G-ORAN Transition
Despite the compelling vision, the path from proprietary LTE networks to a fully open, disaggregated, AI-driven 5G-ORAN infrastructure is far from trivial. Operators and vendors are navigating several significant technical and operational hurdles.
Fronthaul Latency and Transport Requirements
The 7.2x functional split used in ORAN places strict timing requirements on fronthaul transport. One-way latency must stay under 100 µs, which demands a dedicated, synchronised fronthaul network — often fibre-based with IEEE 1588v2 (PTP) for timing distribution. Legacy fronthaul infrastructure was not designed for these constraints.
Multi-Vendor Interoperability Testing
Open interfaces only work if every vendor implements them correctly. In practice, interoperability testing (IOT) between O-RU, O-DU, O-CU, and RIC components from different vendors remains time-consuming, expensive, and often incomplete. ORAN plugfests and test labs (like the O-RAN SC open-source community) are working to close this gap.
LTE Protocol Testing in a 5G/ORAN Context
As LTE eNBs become virtualised and co-deployed within ORAN frameworks, protocol testing methodologies must evolve. Testing the control plane signalling across EN-DC, validating RIC xApp behaviours against LTE KPIs, and verifying SMO configuration of LTE cells all require engineers with cross-domain expertise spanning LTE protocol stacks, 5G NR, and cloud-native network functions.
Security in Open Interfaces
Proprietary, closed interfaces were implicitly more difficult to attack — security through obscurity. Open ORAN interfaces introduce new attack surfaces at the fronthaul, near-RT RIC, and SMO levels. O-RAN Alliance Working Group 11 (WG11) is specifically focused on security protocols, but hardening open RAN deployments remains an active area of work.
8. What Lies Ahead: 6G, AI-Native RAN and Beyond
The 5G-ORAN convergence is not the final chapter — it is the platform on which the next decade of innovation will be built.
AI-Native RAN
3GPP Release 18 (5G-Advanced) has formally introduced AI/ML as a native feature of the RAN specification — not just an add-on through the RIC. This includes AI-based channel estimation, beam management, and positioning. The RIC ecosystem already being built for 5G-ORAN is the staging ground for these capabilities.
6G Research and What It Borrows from ORAN
6G, targeted for 2030 commercialisation under 3GPP Release 20, is expected to adopt disaggregation, cloud-native deployment, and intelligent network control as baseline design principles — not as optional add-ons. The ORAN ecosystem that operators and vendors build today is directly shaping what 6G will look like architecturally.
LTE's Long Tail
LTE will not disappear quietly. IoT devices using LTE-M and NB-IoT are expected to operate well into the 2030s. Enterprises operating private LTE networks in licenced and shared spectrum will continue expanding their deployments. The LTE protocol expertise you build today has a longer shelf life than most engineers assume.
9. Conclusion & Resources
The journey from LTE to 5G and into the ORAN era represents a fundamental change in how wireless networks are designed, built, and operated. LTE gave us the flat, all-IP, high-speed foundation. 5G NR raised the ceiling on speed, latency, and use-case diversity. ORAN is removing the walls — opening up the architecture so that no single vendor controls the entire stack.
For engineers working in this space, the convergence of all three is the defining challenge and opportunity of this decade. Whether you are testing LTE protocol stacks, designing 5G NSA deployments, or learning how to build and deploy xApps on a Near-RT RIC, the underlying principles connect back to the same evolving standard — and the same community of practitioners learning, sharing, and growing together.

Comments
Post a Comment