Distributed Request Control Server Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing traffic control solutions in distributed systems are inflexible and lack accuracy, as they rely on single-machine pre-allocation and do not effectively manage traffic control policies beyond a validity deadline, leading to inefficiencies and reduced control flexibility.

Innovation Solution

A method and apparatus that determine the type of request or object name, acquire the number of control servers in a preset control server set based on a validity deadline, and forward requests to a target control server, using hash calculations for server determination, allowing for flexible and accurate traffic control in a distributed environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If single-machine pre-allocation is used for traffic control, then implementation is simple, but traffic control accuracy and flexibility deteriorate in distributed systems

Engineering Contradiction:
Improveimplementation simplicityVSAvoidtraffic control accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The patent divides the traffic control function into multiple control servers distributed across the system. Each control server is responsible for specific traffic control tasks, allowing the system to maintain simplicity at the individual server level while achieving high accuracy through the collective action of multiple servers. This segmentation resolves the contradiction by distributing the control logic across multiple nodes rather than relying on a single machine.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of control by implementing validity deadlines for request control information. This temporal dimension allows the system to dynamically adjust traffic control policies based on time-sensitive requirements, enhancing both accuracy and flexibility without complicating the basic control mechanism. The validity deadline mechanism adds a time-based layer to the traffic control approach.

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

2Device complexity

If single-machine pre-allocation is used for traffic control, then system structure is simple, but adaptability to different traffic patterns deteriorates

Engineering Contradiction:
Improvesystem structure complexityVSAvoidtraffic control flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal traffic control framework where control servers can handle multiple types of traffic patterns and request types. The system uses a standardized interface and control mechanism that can adapt to different traffic scenarios without requiring complex specialized structures. This universality allows the system to maintain structural simplicity while achieving high adaptability through configurable control policies and the ability to serve multiple functions within the same framework.

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

Solution Approach 2:

The patent implements dynamic traffic control by introducing validity deadlines and time-based control information. The system can dynamically adjust traffic control parameters, redirect requests to different control servers based on current conditions, and update control policies in real-time. This dynamic capability enables the system to adapt to varying traffic patterns without increasing structural complexity, as the changes are achieved through software-based control mechanisms rather than structural modifications.

Inventive Principle:
Principle #15Dynamics

3Speed

If request control information is stored locally without validity deadlines, then access speed is fast, but control accuracy after deadline deteriorates

Engineering Contradiction:
Improverequest access speedVSAvoidcontrol accuracy after validity deadline
Core Design Contradiction:
SpeedVSMeasurement precision

Solution Approach 1:

The patent applies preliminary action by pre-calculating and storing validity deadlines with request control information. This allows the system to quickly determine whether control information is still valid without requiring complex real-time validation logic. The validity deadline is prepared in advance and can be rapidly checked against the current time, maintaining fast access speed while ensuring control accuracy by clearly defining the operational lifespan of each control information item.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the system continuously monitors the current time against stored validity deadlines. When control information approaches or exceeds its validity deadline, the system receives feedback and can take corrective actions such as refreshing the control information or redirecting requests to appropriate control servers. This feedback loop maintains both fast access (through efficient time comparisons) and high accuracy (through automated validity verification).

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10931791B2Method and apparatus for processing request
Publication Date: 2021.02.23 BEIJING BAIDU NETCOM SCI & TECH CO LTD
  • US10931791B2 patent drawing
  • US10931791B2 patent drawing
  • US10931791B2 patent drawing

AI summary

Embodiments of the present disclosure disclose a method and apparatus for processing a request. A specific embodiment of the method includes: receiving a request; determining a type of the request or an object name indicated by the request; acquiring, after determining that a current time is after a validity deadline of locally stored first request control information, the number of control servers in a preset control server set; determining, from the control server set, a target control server based on the acquired number and any one of: the type of the request, the object name indicated by the request; and forwarding the request to the target control server.