vRAN–Core Interface Failure Detection and Reestablishment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communication interfaces in wireless networks, such as N1, N2, and N3 interfaces, often fail due to software upgrades or virtual machine failures, leading to degraded network performance and prolonged service disruptions without effective detection or reestablishment mechanisms.

Innovation Solution

Implementing a system that utilizes a dissective engine to identify failed communication interfaces by analyzing event information, a workflow engine to reestablish these interfaces, and a configuration manager to manage the reestablishment process, maintaining interface states and recording reestablishment data for future predictions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If communication interfaces are monitored and reestablished automatically, then network reliability is improved, but system complexity increases due to additional monitoring and reestablishment mechanisms

Engineering Contradiction:
Improvecommunication interface reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by enabling communication interfaces to automatically detect their own failures and trigger reestablishment procedures without external intervention. The monitoring mechanism allows interfaces to self-diagnose connectivity issues, and the reestablishment process is autonomously initiated by the affected interface or its associated network function, reducing the need for complex external management systems.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system employs feedback mechanisms where monitoring continuously assesses the state of communication interfaces and feeds this information back to the reestablishment logic. When a failure is detected, the feedback loop triggers the reestablishment process, and subsequent monitoring provides feedback on whether the reestablishment was successful, enabling iterative improvement and automatic adaptation without increasing overall system complexity.

Inventive Principle:
Principle #23Feedback

2Loss of time

If automatic reestablishment mechanisms are implemented, then service disruption time is reduced, but the complexity of detecting and measuring interface failures increases

Engineering Contradiction:
Improveservice disruption timeVSAvoidinterface failure detection complexity
Core Design Contradiction:
Loss of timeVSDifficulty of detecting and measuring

Solution Approach 1:

The system applies preliminary action by pre-configuring reestablishment procedures and monitoring rules before failures occur. Interface monitoring is continuously active with pre-defined thresholds and response actions, so when a failure happens, the system can immediately execute the pre-planned reestablishment sequence without needing to analyze or decide in real-time, thus minimizing detection and response complexity while reducing service disruption time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses copying by maintaining configuration templates and procedural blueprints for interface reestablishment. When a failure occurs, instead of creating complex real-time decisions, the system copies proven reestablishment procedures from templates and applies them to the failed interface, simplifying the detection and measurement process while enabling rapid response.

Inventive Principle:
Principle #26Copying

3Productivity

If comprehensive monitoring of communication interfaces is performed, then network performance is improved, but the quantity of data to be processed increases

Engineering Contradiction:
Improvenetwork performanceVSAvoiddata volume
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system extracts only the critical monitoring parameters and essential failure indicators from the comprehensive interface data stream. Instead of processing all available data, the monitoring mechanism selectively extracts key metrics such as connectivity status, error rates, and interface state changes, reducing the volume of data requiring processing while maintaining network performance through focused observation of the most relevant parameters.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial action by monitoring only the essential aspects of interface performance rather than all possible parameters. The monitoring is tuned to detect specific failure modes and critical state changes, processing sufficient data to maintain network performance without the overhead of comprehensive analysis of every data point, thus balancing productivity improvement with manageable data volumes.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250338339A1Systems and methods for identifying and reestablishing failed communication interfaces in a wireless network
Publication Date: 2025.10.30 VERIZON PATENT & LICENSING INC
  • US20250338339A1 patent drawing
  • US20250338339A1 patent drawing
  • US20250338339A1 patent drawing

AI summary

In some implementations, a device may receive event information associated with a virtual radio access network (vRAN) communication failure, identifying, by the device and based on the event information, that a communication interface between a vRAN network function (NF) and a Core network NF has failed. The device may initiate a reestablishment of the communication interface. In a radio access network (RAN) and Core domain, interfaces across various NFs may be key for effective end-to-end communications. Monitoring and identifying communication failures across the RAN and Core with specific event information may be critical. An ability to consider appropriate factors for communication failures may be enabled to dynamically reestablish the communication interface.