vRAN PHY Failure Detection via Programmable Fronthaul Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vRAN systems face challenges in detecting and handling PHY layer failures due to strict real-time latency requirements and high software complexity, leading to service disruptions and inefficiencies in resource allocation.

Innovation Solution

Implementing a programmable switch-based fronthaul middlebox to detect PHY failures by monitoring downlink fronthaul packets and rerouting traffic to a backup server within the same slot duration, leveraging the switch's programmability to minimize CPU overhead and ensure seamless failover.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional specialized hardware is replaced with software-based functionality running on commodity servers, then cost and flexibility are improved, but reliability and real-time performance deteriorate

Engineering Contradiction:
Improvecost and flexibilityVSAvoidreliability and real-time performance
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system segments the vRAN functionality into multiple independent PHY processes running on different commodity servers. Each PHY process handles specific radio units, and failure of one process does not affect others. The programmable switch segments traffic routing to direct packets to specific PHY processes, enabling isolated failure management while maintaining overall system reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the operational parameters by implementing ultra-fast failure detection within a single TTI (500 microseconds) and automatic failover mechanisms. This transforms the reliability parameter by ensuring that even though commodity servers are used, the system achieves hardware-like reliability through rapid detection and switching capabilities that maintain real-time performance requirements.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If failure detection mechanisms are implemented in the control plane, then detection accuracy is improved, but real-time response capability deteriorates due to processing delays

Engineering Contradiction:
Improvedetection accuracyVSAvoidreal-time response capability
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The programmable switch acts as an intermediary between the data plane and control plane. It performs failure detection directly in the data plane by monitoring packet flow patterns and timing, eliminating the need for complex control plane processing. The switch intermediates by implementing lightweight detection logic that achieves both high detection accuracy and real-time response without control plane overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary action by pre-configuring backup PHY processes and routing tables in advance. When a failure is detected, the switch already has backup paths ready, enabling immediate failover without control plane intervention delays. The detection mechanism preliminarily identifies failure patterns through packet timing analysis before actual service disruption occurs.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If complex software-based PHY layer processing is used, then adaptability and feature flexibility are improved, but software complexity and processing overhead increase

Engineering Contradiction:
Improveadaptability and feature flexibilityVSAvoidsoftware complexity and processing overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The programmable switch provides self-service by automatically detecting PHY process failures through packet timing monitoring and autonomously rerouting traffic to backup processes. This eliminates the need for complex software-based failure detection and management in the PHY layer, reducing processing overhead while maintaining adaptability through automated responses.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system substitutes mechanical/software complexity with a simpler architecture by moving failure detection and routing logic to the programmable switch hardware. This replaces complex software-based monitoring and decision-making with hardware-accelerated packet inspection and switching, reducing CPU overhead while preserving software adaptability for PHY processing functions.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If fast failover within a single TTI is implemented, then service continuity is improved, but system complexity and resource requirements increase

Engineering Contradiction:
Improveservice continuityVSAvoidsystem complexity and resource requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements dynamic routing capabilities where the programmable switch can rapidly change packet forwarding paths based on real-time PHY process health status. This dynamic switching enables failover within a single TTI by automatically redirecting traffic to backup processes without manual intervention or complex reconfiguration, achieving service continuity through adaptive routing.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses copying by maintaining backup PHY processes that replicate the functionality of primary processes. These backup processes are pre-configured and ready to immediately take over when a primary process fails. The programmable switch copies routing rules to redirect traffic to appropriate backup processes, enabling fast failover without complex system reconfiguration.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12375341B2Detection of failures in virtualized radio access networks
Publication Date: 2025.07.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12375341B2 patent drawing
  • US12375341B2 patent drawing
  • US12375341B2 patent drawing

AI summary

Data traffic is communicated between a radio unit (RU) of a cellular network and a virtualized radio access network (vRAN) instance of a vRAN. In response to determining that the vRAN instance has failed to communicate a downlink fronthaul packet to the RU within a threshold timeout interval, a failure notification is sent to a PHY layer failure response function. The failure to communicate the downlink fronthaul packet to the RU within the threshold timeout interval is indicative of a failure of the vRAN instance.