Radiolet Network Architecture for Mobile Data Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile data networks face inefficiencies due to high latencies and resource misallocation caused by the 'Mobile Middle Mile' problem, where data traverses multiple switching offices before reaching the subscriber, and lack of end-to-end intelligence between applications and networks, leading to over-provisioning of resources.

Innovation Solution

Implementing a system with 'radiolets' that bring application and content servers closer to subscribers, enabling intelligent cross-layer resource management and flow control, which separates control and data planes, allowing for optimized traffic routing without modifying existing networks or datacenters, and providing network and application awareness to reduce latency and improve resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data traverses multiple switching offices (local, regional, central) to reach the subscriber, then network mobility management and session management are maintained, but latency increases and resource efficiency deteriorates

Engineering Contradiction:
Improvemobility managementVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the network path by introducing intermediate content distribution points between the central switching office and the subscriber. Data is divided into segments that can be cached and delivered from locations closer to the subscriber, reducing the distance traversed while maintaining the hierarchical switching structure for mobility management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary content distribution points and caches at intermediate switching offices. These intermediaries hold copies of popular content locally, allowing data to be delivered from a nearby location rather than traversing the entire path to the central switching office and back, thus reducing latency while preserving network control structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If applications are delivered from centralized datacenters, then resource pooling and management are simplified, but the distance data must travel increases, creating inefficiency

Engineering Contradiction:
Improveresource managementVSAvoiddata path length
Core Design Contradiction:
Device complexityVSLength of stationary object

Solution Approach 1:

The patent implements local quality by placing content distribution points and caches at multiple locations throughout the network infrastructure (at switching offices and intermediate points). This allows content to be delivered from the nearest available cache rather than always from the centralized datacenter, reducing path length while maintaining centralized resource management capabilities.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies preliminary action by pre-caching popular content at intermediate switching offices and content distribution points before actual user requests arrive. This anticipatory caching reduces the distance data must travel when users request content, as copies are already positioned closer to potential subscribers.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If network operators upgrade existing networks to reduce latency, then service quality improves, but capital expenditure and operational costs increase significantly

Engineering Contradiction:
ImprovelatencyVSAvoidoperational cost
Core Design Contradiction:
Loss of timeVSLoss of energy

Solution Approach 1:

The patent uses copying by creating distributed cache copies of content at intermediate network points rather than requiring physical infrastructure upgrades. These software-based copies enable faster local delivery without the capital expenditure associated with building new datacenters or upgrading core network hardware, reducing latency through intelligent data replication.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent employs temporary, software-based cache instances at switching offices that can be dynamically created and removed as needed. These lightweight, virtual cache objects provide latency reduction benefits without requiring permanent, expensive hardware infrastructure, allowing operators to optimize performance on-demand rather than investing in permanent upgrades.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

4Adaptability or versatility

If applications treat the network as a blackbox, then application portability is maintained, but application awareness of network conditions is lost, leading to over-provisioning

Engineering Contradiction:
Improveapplication portabilityVSAvoidresource provisioning
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements feedback mechanisms that provide network state information (such as latency, bandwidth availability, and content location) back to applications. This feedback loop enables applications to adapt their behavior based on actual network conditions, optimizing resource usage without sacrificing portability, as the feedback is provided through standardized interfaces that work across different network environments.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3629557B1System and method of delivering data that provides service differentiation and monetization in mobile data networks
Publication Date: 2021.06.30 ALEF EDGE INC
  • EP3629557B1 patent drawingFigure 1
  • EP3629557B1 patent drawingFigure 2
  • EP3629557B1 patent drawingFigure 3

AI summary

An exemplary system according to the present disclosure comprises a lower tier radiolet™ that is in communication with a local switching office of a mobile data network, and an upper tier radiolet™ that is in communication with the lower tier radiolet™ and an Internet datacenter. In operation, the upper tier radiolet™ receives data extracted from the Internet datacenter and distributes at least a portion of the received data to the lower tier radiolet™. At the lower tier radiolet™, the portion of received data is stored. The lower tier radiolet™ then receives a data request (relating to a portion of received data) and in turn, transmits data from the portion of received data to a source of the data request. The lower tier radiolet™ is located closer to the source of the data request than the Internet datacenter to improve application performance and efficiency of network as well as datacenter.