Interface Data Mapping for Ethernet Fronthaul and CPRI Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge of flexible networking and communication between devices in a 5G network and a distributed base station system is hindered by the use of different interface protocols, such as the Ethernet fronthaul interface protocol and the Common Public Radio Interface (CPRI) protocol, leading to increased network delay and limited compatibility.
Innovation Solution
An interface data processing method that maps and demaps data based on Block Description (BD) information, allowing devices to convert between different data types and protocols, reducing the need for hardware interface conversion devices and enabling direct communication between devices with varying protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different interface protocols (Ethernet fronthaul and CPRI) are used for communication between devices, then device compatibility and networking flexibility are improved, but network delay increases and communication efficiency deteriorates
Solution Approach 1:
The patent introduces a protocol conversion device that acts as an intermediary between devices using different interface protocols (Ethernet fronthaul and CPRI). This mediator translates data between the two protocols, enabling compatibility without requiring direct protocol compatibility between end devices, thus resolving the contradiction between adaptability and communication efficiency.
Solution Approach 2:
The patent changes the protocol parameter (interface type) dynamically based on device capabilities and requirements. By allowing protocol conversion between Ethernet fronthaul and CPRI at the network layer, the system can adapt parameters to achieve both compatibility and efficient communication, resolving the contradiction between versatility and time loss.
2Adaptability or versatility
If protocol conversion devices are introduced to enable communication between different interface protocols, then device compatibility is improved, but system complexity and hardware overhead increase
Solution Approach 1:
The protocol conversion device is designed with multi-functionality, capable of handling both Ethernet fronthaul and CPRI protocols simultaneously. By consolidating protocol conversion capabilities into a single universal device rather than requiring separate conversion hardware for each protocol pair, the system reduces overall hardware overhead while maintaining high protocol compatibility.
Solution Approach 2:
The patent uses virtualization techniques to create virtual protocol conversion instances that can be replicated and distributed across the network. Instead of deploying heavy hardware conversion devices at every network point, lightweight virtual copies of the protocol conversion function are deployed, reducing hardware overhead while maintaining compatibility.
3Adaptability or versatility
If hardware interface conversion devices are used to enable communication between different protocols, then protocol compatibility is improved, but resource overhead and power consumption increase
Solution Approach 1:
The patent replaces traditional hardware-based protocol conversion mechanisms with software-defined protocol conversion running on general-purpose processors or FPGAs. This substitution eliminates the need for dedicated hardware conversion devices, significantly reducing power consumption while maintaining interface compatibility between Ethernet fronthaul and CPRI protocols.
Solution Approach 2:
The protocol conversion system is designed to be dynamic and adaptive, activating conversion functions only when needed based on real-time network conditions and device capabilities. This dynamic approach allows the system to reduce power consumption by disabling unnecessary conversion operations while maintaining compatibility when required.
Data Source
AI summary
The present disclosure provides an interface data processing method, a transmitting-end device and a receiving-end device. The method includes: mapping data to be processed into interface data based on a data type of the data to be processed, a data type which a receiving-end device can process and preset block description information; and sending the interface data to the receiving-end device.


