Consistent Server Hashing for Mobile CPE Data Flow Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data flow management systems between mobile applications and customer premises equipment face challenges such as high latency, excessive CPU usage, and scalability issues due to the reliance on centralized global routing tables and frequent connection disruptions, particularly in large customer bases.

Innovation Solution

Implementing consistent server hashing to connect mobile applications and customer premises equipment to the same server or server group, eliminating the need for a global routing table and allowing for efficient data exchange through local routing tables, thereby reducing dependence on centralized resources and minimizing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized global routing tables are used to manage data flow between mobile applications and customer premises equipment, then routing coverage is comprehensive, but latency increases and CPU usage becomes excessive

Engineering Contradiction:
Improverouting coverageVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the centralized global routing table into multiple distributed local routing tables, one at each server. Each server maintains its own routing information independently, eliminating the need for a single centralized table. This segmentation reduces the lookup path and eliminates centralized bottlenecks, thereby reducing latency while maintaining comprehensive routing coverage across the distributed system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces server hashing as an additional dimension for routing determination. Instead of relying solely on a hierarchical centralized routing structure, the system adds a hash-based direct mapping from customer identifiers to specific servers. This dimensional change enables O(1) routing lookup time, dramatically reducing latency while preserving complete routing coverage through the hash function's deterministic mapping.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If centralized global routing tables are used to manage data flow, then routing information is centralized, but computing power requirements increase and scalability decreases

Engineering Contradiction:
Improverouting information managementVSAvoidcomputing power requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized routing information management function into distributed components at each server. Each server independently maintains and manages its own local routing table, eliminating the need for a single centralized routing information repository. This distribution reduces the computing power burden on any single system while maintaining reliable routing information management across the entire network through decentralized redundancy.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If mobile applications connect intermittently to customer premises equipment, then network flexibility is improved, but service continuity deteriorates and latency increases

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidservice continuity
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing server assignments through server hashing before actual data transmission occurs. When a mobile application connects, the hash-based routing determines the target server in advance, and the system proactively maintains the connection state and routing information at that server. This preliminary preparation ensures that even with intermittent connections, service continuity is maintained because the routing path is predetermined and connection state is preserved at the assigned server.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240380698A1Systems and methods for data flow between mobile applications and customer premises equipment, using a consistent server hash
Publication Date: 2024.11.14 THE ADT SECURITY CORPORATION
  • US20240380698A1 patent drawing
  • US20240380698A1 patent drawing
  • US20240380698A1 patent drawing

AI summary

According to some embodiments, a system for managing customer premises equipment is provided. The system comprises a plurality of server groups, where each server group of the plurality of server groups is associated with a respective one of a plurality of hash values. The system comprises a load balancer that is configured to receive first signaling from a customer premises equipment associated with a first customer, the first signaling indicating a first hash value of the plurality of hash values, determine a first server group of the plurality of server groups to service the customer premises equipment based on the first hash value, select a first server of a plurality of servers in the first server group to service the first message, and route the first signaling to the first server to service the first signaling.