Use Case and Reference Architecture
This JVD solution utilizes Paragon Automation and other network automation tools (for example, python scripts) to enhance an existing 5G xHaul network and reference architecture. This architecture is defined by O-RAN Alliance Working Group 9 in the O-RAN xHaul Packet Switched Architectures and Solutions technical specification [O-RAN.WG9.XPSAAS-R003-v08.00], which establishes the service aspects and requirements for the xHaul plane.
Paragon Automation and a DHCP/bootstrap server, (for example, open DHCP server), both located at the Service Edge location, can help and provide value to a 5G network by automating the onboarding, configuration, provisioning, and monitoring of the xHaul devices.
Paragon Automation can reduce the manual effort and human errors involved in managing a large and complex network, and ensures that the network is optimized for performance, reliability, and security. Paragon Automation can also enable faster deployment and troubleshooting of new services and technologies, such as slicing, edge computing, and network function virtualization. By using Paragon Automation, service operators can leverage the benefits of 5G and deliver better customer experience.
Efficient onboarding of access node devices is a critical component of this network deployment. Leveraging a DHCP server simplifies and accelerates this process by automating IP address assignment, configuration provisioning, and device registration at Paragon Automation. DHCP server is configured to provide options related to IP addresses, GW, DNS, static routes when onboarding access devices.
Through strategic implementation and use of cutting-edge tools, one can aim to enhance operational efficiency, reduce manual intervention, and ensure a resilient and responsive network infrastructure.
The topology used to validate this design, as mentioned at the beginning of the document, is the same lab topology used in the 5G Fronthaul JVD solution ( Low Latency QoS Design for 5G Solution ), but including a DHCP server and the Paragon Automation system which will be connected via OOB to the Core and Service Edge sections. Access nodes do not have OOB access and connection to both DHCP and Paragon is done via in-band. See below diagram explaining it.
