Relay Node Architecture for Transparent eNodeB Tunneling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing relay nodes in radio access networks are not transparent to eNodeB, require modifications to eNodeB and EPC elements, and incur additional costs due to complex architecture and vendor dependencies, limiting their efficiency and cost-effectiveness, especially at the cell edge.

Innovation Solution

A relay node architecture that tunnels user equipment (UE) messages and data over evolved packet system (EPS) bearers, prioritizing control messages over data, without modifying eNodeB, UE, or EPC elements, enabling mobility support, full duplex capability, and reusable spectrum configuration, while avoiding vendor dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If traditional relay nodes are deployed to extend coverage and enhance cell edge performance, then coverage and capacity are improved, but device complexity and cost increase due to non-transparent architecture and vendor dependencies

Engineering Contradiction:
Improvecoverage areaVSAvoidrelay node architecture complexity
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

The patent creates a virtual copy of the eNodeB functionality within the relay node. The relay node runs a virtual eNodeB instance that implements the same protocol stack and control plane functions as a real eNodeB, allowing it to operate transparently in the network. This virtualization approach enables the relay to provide full eNodeB capabilities without requiring complex hardware modifications or vendor-specific implementations.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The relay node is designed to perform multiple functions: it acts as both a user equipment (connecting to the donor eNodeB) and a base station (serving relayed UEs). The virtual eNodeB implementation allows the same hardware platform to fulfill multiple roles, reducing overall system complexity and eliminating the need for separate vendor-specific relay implementations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If relay nodes with full protocol stack and cell identity are implemented, then mobility support and network transparency are improved, but manufacturing cost and deployment complexity increase

Engineering Contradiction:
Improvemobility support capabilityVSAvoidrelay node deployment cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent replaces traditional hardware-based protocol implementation with software-defined virtualization. Instead of requiring specialized hardware circuits for protocol processing, the relay node uses software-based virtual eNodeB instances that run on general-purpose computing platforms. This substitution dramatically reduces manufacturing costs while maintaining full protocol stack functionality for mobility support.

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

Solution Approach 2:

The patent changes the fundamental parameter of relay node implementation from hardware-specific to software-defined. By virtualizing the eNodeB function, the system transforms fixed hardware capabilities into flexible software parameters that can be configured and deployed without expensive hardware modifications, enabling cost-effective deployment while maintaining full mobility support.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If vendor-specific relay implementations are used, then initial deployment is achieved, but adaptability and ease of repair worsen due to vendor dependencies

Engineering Contradiction:
Improvenetwork compatibilityVSAvoidvendor support dependency
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The virtual eNodeB implementation enables the relay node to autonomously manage its own protocol stack and control plane functions without requiring vendor-specific support. The software-based architecture allows operators to independently configure, maintain, and repair relay nodes using standard virtualization management tools, eliminating dependency on proprietary vendor services while maintaining full network compatibility.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10205507B2Relay architecture, relay node, and relay method thereof
Publication Date: 2019.02.12 TEJAS NETWORKS LTD
  • US10205507B2 patent drawing
  • US10205507B2 patent drawing
  • US10205507B2 patent drawing

AI summary

In an aspect, the present disclosure relates to a relay node (RN) operatively coupled with user equipment (UE), wherein the RN is configured to create one or more tunnels to enable transmission of data messages and control messages from the UE directly to a packet data network gateway (PGW). The present disclosure relates to methods and systems for tunneling user equipment (UE) traffic by creating one or more tunnels between a relay node (RN) and packet data network gateway (PGW) to prioritize control messages over data messages, wherein the one or more tunnels are created when the UE gets attached to the relay node (RN). Further, tunneling of the one or more control/non-access stratum (NAS) messages to the PGW can be performed over one of the higher priority tunnels such that when the NAS messages are received at the PGW or HGW, they can be forwarded to a mobility management entity (MME).