Hybrid LAN Gateway for 5G Non-5G Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack efficient communication between 5G enabled devices and non-5G enabled devices, as communication signals often require routing through a headend, leading to delays and inefficiencies, especially for internal communication within a local domain.

Innovation Solution

A hybrid platform is established to create a hybrid system Local Area Network (LAN) that enables direct communication between 5G enabled devices and non-5G enabled devices by establishing separate connections and using peer-to-peer communication for inbound signals within the local domain, while routing outbound signals to public cloud servers, optimizing data paths and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If communication between 5G enabled devices and non-5G enabled devices is routed through a headend, then connectivity between different device types is achieved, but latency increases and communication efficiency deteriorates

Engineering Contradiction:
ImproveconnectivityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a gateway as an intermediary component that enables direct peer-to-peer communication between 5G enabled devices and non-5G enabled devices within the local domain. The gateway translates and routes communications locally without requiring headend involvement, thereby maintaining connectivity while eliminating the latency associated with headend routing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network communication path by creating a local domain segment that handles communications between 5G and non-5G devices independently. This segmentation allows local communications to bypass the headend entirely, reducing latency while maintaining overall system connectivity through the gateway.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If headend routing is used for all communications, then centralized control is maintained, but communication efficiency and network performance deteriorate

Engineering Contradiction:
Improvecentralized controlVSAvoidcommunication efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements local quality by enabling peer-to-peer communication within the local domain through the gateway, allowing communications to be handled locally without centralized headend intervention. This maintains centralized control architecture while improving communication efficiency for local traffic by processing it distributedly at the gateway level.

Inventive Principle:
Principle #3Local quality

3Productivity

If a hybrid platform with separate connections is established, then communication efficiency between 5G and non-5G devices is improved, but device complexity increases

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The gateway is designed with multi-functionality to handle communications between 5G enabled devices and non-5G enabled devices through a single unified interface. This universal gateway approach improves communication efficiency while minimizing system complexity by consolidating multiple connection types into one versatile component rather than requiring separate specialized devices for each device type.

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

Data Source

PatentUS10925105B2Hybrid system local area network
Publication Date: 2021.02.16 BANK OF AMERICA CORP
  • US10925105B2 patent drawing
  • US10925105B2 patent drawing
  • US10925105B2 patent drawing

AI summary

An electronic system is typically configured for crawling, via a machine learning model, into one or more API servers, wherein the one or more API servers comprise one or more versions of one or more APIs, capturing, via the machine learning model, information associated with the one or more versions of the one or more APIs, creating context objects associated with each of the one or more versions of the one or more APIs, receiving a real-time API request from a client system, processing the real-time API request received from the client system, and routing the real-time API request to an API version of the one or more versions.