Split Cloud RAN Architecture for Low Latency Edge Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud RAN systems face challenges in meeting low latency requirements for 5G applications due to fronthaul latency, leading to overprovisioning and increased costs, especially when handling latency-sensitive applications that require sub-millisecond latency.
Innovation Solution
A split cloud RAN architecture is implemented, where a local cloud RAN processes latency-sensitive applications with a local scheduler and a remote cloud RAN processes latency-tolerant applications, using different waveform numerologies and resource allocation strategies to optimize resource usage and reduce costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If cloud RAN processes all applications remotely, then operation cost is reduced due to resource pooling, but latency requirement for low latency applications cannot be met
Solution Approach 1:
The patent segments the RAN processing into two distinct parts: a local cloud RAN component that handles latency-sensitive applications and a remote cloud RAN component that handles latency-tolerant applications. This segmentation allows each component to be optimized for its specific function, with the local component providing low latency service and the remote component providing cost-efficient resource pooling.
Solution Approach 2:
The patent applies local quality by deploying specific processing capabilities locally at the edge network to handle latency-sensitive applications, while maintaining centralized remote processing for latency-tolerant applications. This ensures that each location has the appropriate quality and capability level needed for its specific workload.
2Loss of time
If local cloud RAN is deployed to meet latency requirements, then low latency applications are supported, but overprovisioning occurs and costs increase
Solution Approach 1:
The patent implements dynamic resource allocation where the local cloud RAN and remote cloud RAN can flexibly adjust their processing loads based on real-time application requirements. This dynamic approach allows the system to provision resources only when and where needed, avoiding static overprovisioning while maintaining latency performance for critical applications.
Solution Approach 2:
The patent creates a universal architecture where a single distributed RAN system can handle both latency-sensitive and latency-tolerant applications through different processing paths. This multi-functionality eliminates the need for separate dedicated infrastructure for different application types, reducing overall provisioning costs.
3Productivity
If remote cloud RAN processes latency-tolerant applications, then resource pooling efficiency is improved, but fronthaul latency adds delay
Solution Approach 1:
The patent extracts the fronthaul communication requirement from the processing path of latency-tolerant applications by handling these applications exclusively through the remote cloud RAN. This separation ensures that applications insensitive to fronthaul latency can fully benefit from remote resource pooling without being constrained by transmission delays.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There is provided a system that includes a local cloud radio access network (RAN), and a remote cloud RAN. The local cloud RAN processes latency-sensitive applications, and the remote cloud RAN processes latency-tolerant applications. User traffic is appropriately routed to the correct cloud RAN based on the application. User equipment (UE) has no knowledge of which network is being used for processing, i.e., this network processing split is done in a manner that is transparent to the UE, e.g., by dynamically selecting a different access point name for local vs. remote processing. The processing split of the RAN between the local cloud RAN and the remote cloud RAN is done in a dynamic manner depending on the number of devices requiring low latency support. This allows the local cloud RAN to be very compact and low-cost since it does not have to process the latency -tolerant traffic.