Distributed Unit Zero-Touch Integration via Proxy Central Unit
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G RAN architecture lacks automation in configuring distributed units (DUs) with F1 Transport Network Layer (TNL) IP addresses, requiring manual configuration and lacking support for zero-touch deployment, which complicates the integration of DUs with central units (CUs).
Innovation Solution
Implementing a method where the distributed unit performs a DNS lookup for a proxy central unit to automatically discover the F1-C TNL address, eliminating the need for manual configuration and enabling zero-touch integration by establishing a connection using the received IP address of the central unit.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual configuration of F1 TNL IP addresses is used for distributed units, then configuration control is maintained, but deployment complexity increases and automation is lost
Solution Approach 1:
The distributed unit performs self-configuration by automatically discovering the F1-C TNL address of the central unit through DNS lookup and initiating configuration transfer procedure, eliminating the need for manual IP address configuration and enabling zero-touch deployment
Solution Approach 2:
A proxy central unit is introduced as an intermediary to facilitate the configuration transfer procedure between the distributed unit and the core network, enabling automated discovery and connection establishment without manual intervention
2Productivity
If manual IP address configuration is required for DUs, then network control is maintained, but integration time increases
Solution Approach 1:
The distributed unit automatically obtains the F1-C TNL address of the central unit through DNS lookup and completes the configuration transfer procedure without manual intervention, significantly reducing integration time and enabling rapid deployment
Solution Approach 2:
The system performs preliminary DNS configuration to resolve the fully qualified domain name of the proxy central unit before the distributed unit needs to connect, enabling automatic discovery and connection establishment without manual IP address configuration
3Ease of manufacture
If automated DNS-based discovery is implemented, then deployment simplicity improves, but system architecture complexity increases
Solution Approach 1:
A proxy central unit is introduced as an intermediary component that handles the configuration transfer procedure between the distributed unit and the core network, managing the DNS-based discovery process and enabling automated deployment without significantly increasing overall system complexity
Solution Approach 2:
The proxy central unit serves multiple functions including acting as a DNS resolver for F1-C TNL address discovery, a configuration transfer intermediary, and a connection manager, consolidating multiple responsibilities into a single component that simplifies the overall deployment process
Data Source
AI summary
Embodiments herein relate to a method performed by a distributed unit of a network node, for establishing a connection between the distributed unit and a central unit connected to a core part of the wireless network. The network node includes the central unit and at least the distributed unit. The distributed unit performs a Domain Name Server lookup for a proxy central unit, which will act as a temporary or initial central unit with regard to a configuration transfer procedure. The distributed unit further receives an ip address of the proxy central unit and initiates the configuration transfer procedure by sending a configuration transfer message to the ip address of the proxy central unit. The distributed unit further receives an ip address of the central unit and establishes a connection between the distributed unit and the central unit using the received ip address of the central unit.


