DRAN DU Deployment via Timing Manager Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Distributed Radio Access Network (DRAN) Distributed Units (DUs) in Open RAN architectures face challenges such as fixed capacity limitations, static hardware boundaries, and difficulties in automated deployment and configuration, leading to inefficiencies and load imbalances, especially in varying urban and rural environments.
Innovation Solution
A method for deploying DRAN DUs involves receiving deployment status from a cloud server, triggering a timing manager service instantiation, determining timing synchronization status, deploying DU Network Functions based on synchronization status, and configuring these functions using a configuration manager service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If conventional DUs are deployed with fixed capacity and static hardware boundaries, then each DU can be independently provisioned, but severe load imbalance occurs between rural and urban areas
Solution Approach 1:
The patent segments the DU into two independent functional units: CU (Centralized Unit) and RU (Radio Unit). The CU handles higher-layer protocols and can be centrally located, while the RU handles radio frequency operations and is distributed at cell sites. This segmentation allows flexible allocation of computational resources to balance load between urban and rural areas while maintaining independent provisioning capabilities.
Solution Approach 2:
The patent introduces a new architectural dimension by separating control plane functions (CU) from user plane functions (RU), enabling multi-dimensional resource allocation. This allows the system to optimize for both centralization benefits (load balancing) and distribution benefits (independent provisioning) simultaneously by operating in different functional dimensions.
2Adaptability or versatility
If DRAN DUs are disaggregated with each DU provisioned for each Radio Unit, then network functionality is further distributed, but provisioning and maintenance becomes challenging
Solution Approach 1:
The patent creates a universal CU that can manage multiple RUs through standardized interfaces. The CU implements generic higher-layer protocols (RRC, PDCP, RLC) that can serve different RU types and configurations, enabling multi-functional operation. This universality simplifies provisioning and maintenance by providing a single point of control for disaggregated network functions while maintaining adaptability across different deployment scenarios.
Solution Approach 2:
The CU acts as an intermediary between the core network and distributed RUs, mediating control plane and user plane traffic. This intermediary layer abstracts the complexity of managing multiple disaggregated RUs, providing centralized configuration, monitoring, and maintenance capabilities while preserving the benefits of distributed radio access.
3Productivity
If centralized CU operates multiple distributed RUs, then network competitiveness and coverage are improved, but fixed DU capacity creates hard limits on deployment benefits
Solution Approach 1:
The patent enables dynamic resource allocation between CU and RU based on real-time traffic conditions and service requirements. The flexible architecture allows the CU to dynamically adjust the number and configuration of connected RUs, enabling the network to adapt to varying urban and rural deployment needs without fixed capacity constraints, thereby maintaining both high productivity and deployment flexibility.
Data Source
AI summary
Embodiments of the present disclosure disclose method and system for deploying Distributed Radio Access Network (DRAN) Distributed Units (DUs) 102c in an Open RAN architecture 100 is disclosed. The method comprises receiving, a deployment status of a DU cluster from a cloud server 103; triggering a timing manager service instantiation on the DU cluster based on the deployment status of the DU cluster; determining a timing synchronization status of the timing manager service; deploying one or more DU Network Functions (NFs) 102c on the DU cluster based on the timing synchronization status of the timing manager service; and deploying a configuration manager service on the DU cluster for configuring the one or more DU NFs 102c.